avsc
Avro for JavaScript
2
Versions
MIT
License
No
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
mtth
Keywords
apiavdlavpravroavscbinarybufferdatadecodingencodingidlinterfaceipcjsonmarshallingmessageprotocolrpcschemaserdeserializationtype
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:new-function-constructor | AI (semgrep): avsc uses new Function() for schema-driven RPC stub generation — a documented, intentional pattern in this Avro library, not arbitrary code execution from user input. | ai | |
| provenance | no-provenance | AI (provenance): Established 10+ year old package; absence of Sigstore provenance is expected for packages predating the feature and is not a risk signal here. | ai |
v5.7.9
1 finding
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.
v5.7.8
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.