@agoric/casting
Agoric's OCap broadcasting system
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@endo/init | AI (phantom-deps): Transitive dependency used in Agoric's initialization pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@endo/lockdown | AI (phantom-deps): Transitive dependency used in Agoric's initialization pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@endo/promise-kit | AI (phantom-deps): Transitive dependency used in Agoric's initialization pattern; stable false positive. | ai | |
| phantom-deps | phantom-dep:@cosmjs/proto-signing | AI (phantom-deps): Declared dependency used transitively; stable false positive for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 13 / 7 | |
| 0.4.2 | 14 / 6 | |
| 0.4.1 | 14 / 6 | |
| 0.4.0 | 14 / 6 | |
| 0.3.4 | 12 / 5 | |
| 0.3.3 | 12 / 5 | |
| 0.3.2 | 12 / 5 | |
| 0.3.1 | 12 / 5 | |
| 0.3.0 | 12 / 5 | |
| 0.2.0 | 12 / 5 |
v0.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.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 (warner) than the most recent previously approved version (jimlarson) on 2023-05-24, but warner 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.0
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 (warner) than the most recent previously approved version (jimlarson) on 2023-05-19, but warner 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.3.4
2 findingsThis version was published by a different npm account (jimlarson) than the most recent previously approved version (warner) on 2023-02-17. It has since remained available on npm for 1255 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.