typescript-language-server
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate transition to GitHub Actions CI/CD publishing with SLSA provenance attestation. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived package moved to CI/CD; SLSA provenance confirms legitimate publish. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): typescript-language-server spawns tsserver as a child process by design; child_process usage is core functionality for this LSP wrapper. | ai | |
| semgrep | semgrep:env-bulk-read | AI (semgrep): Env enumeration is used to pass the current environment to spawned npm/tsserver processes, a standard pattern for process-launching tools. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.3.0 | 0 / 39 | |
| 5.2.0 | 0 / 39 | |
| 5.1.3 | 0 / 36 | |
| 5.1.2 | 0 / 36 | |
| 5.1.1 | 0 / 36 | |
| 5.1.0 | 0 / 36 | |
| 5.0.1 | 0 / 36 | |
| 5.0.0 | 0 / 36 |
v5.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-10. 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.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.