sharedb
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | url-dep:ot-json0-v2 | AI (npm-metadata): SHA-pinned dep is in devDependencies only; not shipped to consumers, no runtime risk. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 6.0.1 | 5 / 12 | |
| 6.0.0 | 5 / 12 | |
| 5.2.2 | 5 / 12 | |
| 5.2.1 | 5 / 12 | |
| 5.2.0 | 5 / 12 | |
| 5.1.1 | 5 / 12 | |
| 5.1.0 | 5 / 12 | |
| 5.0.4 | 5 / 12 | |
| 5.0.3 | 5 / 12 | |
| 5.0.2 | 5 / 12 | |
| 5.0.1 | 5 / 12 |
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
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.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.