twoslash
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/shared/twoslash.D2-zMJku.cjs | AI (source-diff): Standard bundled build output with long lines; not obfuscated. Stable for this package. | ai | |
| source-diff | obfuscated-file:dist/shared/twoslash.DtmOPsj_.mjs | AI (source-diff): Standard bundled build output with long lines; not obfuscated. Stable for this package. | ai | |
| dependencies | unvetted-dep:@typescript/vfs | AI (dependencies): @typescript/vfs is an official Microsoft/TypeScript team package; a stable, legitimate dependency for this TypeScript tooling package. | ai | |
| dependencies | unvetted-dep:twoslash-protocol | AI (dependencies): twoslash-protocol is a sibling package in the same monorepo, always published at the same version; not an independent risk. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.3.8 | 2 / 1 | |
| 0.3.7 | 2 / 1 | |
| 0.3.6 | 2 / 1 | |
| 0.3.4 | 2 / 1 | |
| 0.3.3 | 2 / 1 | |
| 0.3.2 | 2 / 1 |
v0.3.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.4
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly 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.
v0.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.