@sphereon/ssi-types
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/index.d.cts | AI (source-diff): tsup-generated CJS TypeScript declaration file; long lines are concatenated type defs, not obfuscation. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:dcql | AI (phantom-deps): dcql is a declared runtime dependency; phantom-dep heuristic fires but it is legitimately used by this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Sphereon package; no provenance is consistent across their entire published catalog. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.40.0 | 9 / 4 | |
| 0.39.0 | 9 / 4 | |
| 0.38.0 | 9 / 4 | |
| 0.37.1 | 9 / 4 | |
| 0.37.0 | 9 / 4 | |
| 0.36.0 | 9 / 4 | |
| 0.34.0 | 7 / 4 | |
| 0.33.0 | 7 / 7 |
v0.40.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.39.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.38.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.36.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.