@tsd/typescript
TypeScript with some extras for type-checking.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:typescript/lib/_tsc.js | AI (source-diff): typescript/lib/_tsc.js is the official Microsoft TypeScript compiler bundle (esbuild output), clearly identified by its Apache 2.0 copyright header and version strings. Long lines are minification artifacts, not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from samverschueren to GitHub Actions CI/CD is a legitimate maintainer workflow change, confirmed by SLSA provenance attestation. Generalizes to future versions. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process in tsserver is expected — TypeScript's language server legitimately spawns child processes. This is core TypeScript functionality from Microsoft's codebase. | ai |
Versions (showing 51 of 57)
| Version | Deps | Published |
|---|---|---|
| 6.0.3 | 0 / 7 | |
| 6.0.2 | 0 / 7 | |
| 5.9.3 | 0 / 7 | |
| 5.9.2 | 0 / 7 | |
| 5.8.3 | 0 / 7 | |
| 5.8.2 | 0 / 7 | |
| 5.7.3 | 0 / 7 | |
| 5.7.2 | 0 / 7 | |
| 5.6.3 | 0 / 7 | |
| 5.6.2 | 0 / 7 | |
| 5.5.4 | 0 / 7 | |
| 5.5.3 | 0 / 7 | |
| 5.5.2 | 0 / 7 | |
| 5.4.5 | 0 / 7 | |
| 5.4.4 | 0 / 7 | |
| 5.4.3 | 0 / 7 | |
| 5.3.3 | 0 / 7 | |
| 5.3.2 | 0 / 7 | |
| 5.2.2 | 0 / 7 | |
| 5.1.6 | 0 / 7 | |
| 5.1.5 | 0 / 7 | |
| 5.1.3 | 0 / 7 | |
| 5.0.4 | 0 / 7 | |
| 5.0.3 | 0 / 7 | |
| 5.0.2 | 0 / 7 | |
| 4.9.5 | 0 / 7 | |
| 4.9.4 | 0 / 7 | |
| 4.9.3 | 0 / 7 | |
| 4.8.4 | 0 / 7 | |
| 4.8.3 | 0 / 7 | |
| 4.8.2 | 0 / 7 | |
| 4.7.4 | 0 / 7 | |
| 4.7.3 | 0 / 7 | |
| 4.7.2 | 0 / 7 | |
| 4.6.4 | 0 / 7 | |
| 4.6.3 | 0 / 7 | |
| 4.6.2 | 0 / 7 | |
| 4.5.5 | 0 / 7 | |
| 4.5.4 | 0 / 7 | |
| 4.5.3 | 0 / 7 | |
| 4.5.2 | 0 / 7 | |
| 4.4.4 | 0 / 7 | |
| 4.4.3 | 0 / 7 | |
| 4.4.2 | 0 / 7 | |
| 4.3.5 | 0 / 7 | |
| 4.3.4 | 0 / 7 | |
| 4.3.3 | 0 / 7 | |
| 4.3.2 | 0 / 7 | |
| 4.2.4 | 0 / 7 | |
| 4.1.5 | 0 / 7 | |
| 4.0.7 | 0 / 7 |
v6.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.2
2 findingsThis version was published by a different npm account than previous versions on 2026-03-25. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.3
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.