@injectivelabs/tc-abacus-proto-ts-v2
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@protobuf-ts/grpcweb-transport | AI (phantom-deps): Declared runtime dependency; phantom-dep heuristic false positive for proto-ts packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Generated proto package; inflated semver and missing description are expected patterns. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.18.6 | 3 / 0 | |
| 1.18.5 | 3 / 0 | |
| 1.18.4 | 3 / 0 | |
| 1.18.3 | 3 / 0 | |
| 1.18.2 | 3 / 0 | |
| 1.18.1 | 3 / 0 |
v1.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.