@agoric/store
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:@agoric/marshal | AI (dependencies): Internal Agoric monorepo sibling package, not third-party. | ai | |
| npm-metadata | url-dep:esm | AI (npm-metadata): Known agoric-labs esm fork used across the org's packages, devDependency only. | ai | |
| phantom-deps | phantom-dep:@endo/promise-kit | AI (phantom-deps): Monorepo package; likely used via re-export patterns not caught by import scan. | ai | |
| phantom-deps | phantom-dep:@endo/eventual-send | AI (phantom-deps): Monorepo package; likely used via re-export patterns not caught by import scan. | ai | |
| dependencies | unvetted-dep:@agoric/assert | AI (dependencies): First-party Agoric monorepo sibling package, same publisher/org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): kriskowal is a known Agoric core maintainer; benign addition. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 0.10.0 | 5 / 3 | |
| 0.7.1 | 4 / 3 | |
| 0.4.23 | 2 / 4 | |
| 0.4.18 | 2 / 4 | |
| 0.4.16 | 2 / 4 | |
| 0.0.2 | 2 / 4 | |
| 0.0.1 | 2 / 4 |
v0.7.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (michaelfig) than the most recent previously approved version (katesills) on 2022-05-09, but michaelfig is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.23
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (michaelfig) than the most recent previously approved version (katesills) on 2021-07-28, but michaelfig is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.18
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (michaelfig) than the most recent previously approved version (katesills) on 2021-06-24, but michaelfig is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (michaelfig) than the most recent previously approved version (katesills) on 2020-03-26, but michaelfig is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.