@launchql/protobufjs
1
Versions
—
License
Yes
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
pyramation
Keywords
protobufprotocol-buffersserializationtypescript
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): Canonical protobuf.js postinstall; reads own package.json to check version scheme, no network or arbitrary execution. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves only to the package's own package.json — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:long | AI (phantom-deps): long is a declared runtime dep used by protobuf.js consumers; phantom-dep heuristic misfires here. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Type-only dependency; not directly imported by convention — stable false positive. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 7.2.6 | 12 / 30 |
v7.2.6
2 findings
HIGH
Package has 'postinstall' script
install-scripts
Script: node scripts/postinstall
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.