@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@sphereon/kmp-mdl-mdoc | AI (dependencies): Same-org first-party dep from Sphereon monorepo. | ai | |
| dependencies | unvetted-dep:@sphereon/ssi-sdk-ext.jwt-service | AI (dependencies): Same-org first-party dep from Sphereon monorepo. | ai | |
| phantom-deps | phantom-dep:@sphereon/ssi-sdk-ext.jwt-service | AI (phantom-deps): Same-org scope, likely used indirectly; low risk. | ai | |
| 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 43 of 43)
| Version | Deps | Published |
|---|---|---|
| 0.40.1 | 9 / 4 | |
| 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 | |
| 0.32.0 | 6 / 7 | |
| 0.31.0 | 6 / 7 | |
| 0.30.1 | 6 / 7 | |
| 0.29.0 | 4 / 7 | |
| 0.28.0 | 4 / 7 | |
| 0.27.0 | 4 / 7 | |
| 0.26.0 | 4 / 7 | |
| 0.25.0 | 4 / 7 | |
| 0.24.0 | 2 / 7 | |
| 0.23.4 | 2 / 7 | |
| 0.23.0 | 2 / 7 | |
| 0.22.0 | 2 / 7 | |
| 0.21.1 | 2 / 7 | |
| 0.21.0 | 2 / 7 | |
| 0.19.0 | 2 / 7 | |
| 0.18.1 | 2 / 7 | |
| 0.18.0 | 2 / 7 | |
| 0.17.5 | 1 / 7 | |
| 0.17.4 | 1 / 7 | |
| 0.17.3 | 1 / 7 | |
| 0.17.2 | 1 / 7 | |
| 0.17.1 | 1 / 7 | |
| 0.17.0 | 1 / 7 | |
| 0.16.0 | 1 / 7 | |
| 0.15.1 | 1 / 7 | |
| 0.15.0 | 1 / 7 | |
| 0.14.1 | 1 / 7 | |
| 0.14.0 | 1 / 7 | |
| 0.13.0 | 1 / 7 | |
| 0.12.0 | 1 / 7 | |
| 0.11.0 | 1 / 5 | |
| 0.10.0 | 1 / 5 | |
| 0.9.0 | 1 / 6 | |
| 0.8.0 | 0 / 1 |
v0.40.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.32.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.31.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.29.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.28.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.27.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.25.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.