proto3-json-serializer
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:protobufjs | AI (dependencies): protobufjs is the core dependency this package is explicitly designed to extend; its use is expected and legitimate across all versions of proto3-json-serializer. | ai | |
| provenance | no-provenance | AI (provenance): Google-maintained package published via google-wombot automation; lack of Sigstore provenance is not a meaningful risk signal for this established publisher. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 3.0.4 | 1 / 13 | |
| 3.0.3 | 1 / 13 | |
| 3.0.2 | 1 / 13 | |
| 3.0.1 | 1 / 13 | |
| 3.0.0 | 1 / 13 | |
| 2.0.2 | 1 / 13 | |
| 2.0.1 | 1 / 12 | |
| 2.0.0 | 1 / 12 |
v3.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.