@injectivelabs/core-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, 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 |
|---|---|---|---|---|
| source-diff | large-new-source-files | AI (source-diff): Expected for generated protobuf/gRPC bindings package. | ai | |
| phantom-deps | phantom-dep:@protobuf-ts/grpcweb-transport | AI (phantom-deps): Used indirectly via config/codegen, not a direct import concern. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.20.1 | 3 / 0 | |
| 1.20.0 | 3 / 0 | |
| 1.19.0 | 3 / 0 | |
| 1.18.0 | 3 / 0 | |
| 1.17.3 | 3 / 0 | |
| 1.17.2 | 3 / 0 | |
| 1.17.1 | 3 / 0 | |
| 1.17.0 | 3 / 0 |
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.