Skip to content

Commit 82624d3

Browse files
committed
Sync open source content 🐝 (from 2d4738909e56adc65f4591e3b512c367464ae60a)
1 parent 0fed61e commit 82624d3

File tree

2 files changed

+28
-0
lines changed

2 files changed

+28
-0
lines changed

_meta.global.tsx

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -591,6 +591,9 @@ const meta = {
591591
"standalone-functions": {
592592
title: "Standalone functions",
593593
},
594+
"dependency-management": {
595+
title: "Dependency management",
596+
},
594597
},
595598
},
596599
python: {
Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,25 @@
1+
---
2+
title: "TypeScript dependency management"
3+
description: "Learn how to manage dependencies in Speakeasy-generated TypeScript SDKs to ensure security and stability."
4+
---
5+
6+
# TypeScript dependency management
7+
8+
Generated TypeScript SDKs include dependencies that require ongoing maintenance to ensure security and stability.
9+
10+
## Set up automated dependency scanning
11+
12+
We strongly recommend configuring a dependency scanning tool on your SDK repository. If your organization already uses a scanning tool, configure it for your SDK repository as well. Popular options include [Dependabot](https://docs.github.com/en/code-security/dependabot) (GitHub native), [Snyk](https://snyk.io/), and [Semgrep](https://semgrep.dev/). These tools automatically monitor your dependencies and create pull requests when updates are available.
13+
14+
## Keep dependencies updated
15+
16+
For TypeScript SDKs, lock files like `package-lock.json` freeze dependency versions at SDK generation time. To refresh to the latest secure versions:
17+
18+
```bash
19+
rm -rf package-lock.json && rm -rf node_modules
20+
npm install
21+
```
22+
23+
## Adopt dependency cooldowns
24+
25+
Consider implementing a dependency cooldown strategy where you wait a period (for example, 7-14 days) before adopting newly-published package versions. This practice helps protect against supply chain attacks. Recent incidents have shown that compromised packages are often caught and removed within the first few days of publication. A cooldown period allows the community to vet new releases before they enter your codebase.

0 commit comments

Comments
 (0)