@injectivelabs/chain-api
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:google-protobuf | AI (phantom-deps): Used via generated gRPC bindings, not direct import. | ai | |
| phantom-deps | phantom-dep:@injectivelabs/grpc-web | AI (phantom-deps): Same-org dependency referenced by generated code. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.9.35 | 2 / 0 | |
| 1.9.31 | 2 / 0 | |
| 1.9.28 | 2 / 0 | |
| 1.9.24 | 2 / 0 |
v1.9.31
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 (thomasralee) than the most recent previously approved version (albertchon) on 2024-07-15, but thomasralee 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.
v1.9.28
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 (bangjelkoski) than the most recent previously approved version (albertchon) on 2024-06-17, but bangjelkoski 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.