json-schema-serializer
Plain JS object to JSON serializer give a predefined rigid schema.
3
Versions
Unlicense
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
streamich
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:ts-node | AI (phantom-deps): ts-node is a build/dev tool referenced in config; phantom-dep pattern is expected for build tooling. | ai | |
| phantom-deps | phantom-dep:benchmark | AI (phantom-deps): benchmark is a declared dev dependency used for performance testing; phantom-dep is expected for test/benchmark utilities. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): eval() is used to compile schema-derived serializer functions at runtime — a standard pattern in high-performance JSON serializers. Input is schema-controlled, not user-supplied arbitrary code. | ai |
v1.0.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
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.
v1.0.0
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.