← Home

fast-json-stringify

npm Repository Homepage

Stringify your JSON at max speed

100
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

jsumnersdelvedormatteo.collinaeommclimba03003zekthgurgundayivan-tymoshenkosimonebfdawgsmetcoder95

Keywords

jsonstringifyschemafast

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:child-process-import AI (semgrep): child_process usage is in a benchmark utility script (bench-cmp-branch.js), not runtime code. Stable false positive for this package. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() is the core design of fast-json-stringify for compiling schema-based serializers. Intentional, documented, and stable across all versions. ai
provenance publisher-changed AI (provenance): climba03003 is a known Fastify org contributor with 298 approved packages; transition from eomm is a legitimate maintainer change within the Fastify ecosystem. ai

Versions (showing 100 of 168)

Version Deps Published
7.0.1 6 / 14
7.0.0 6 / 14
6.4.0 6 / 14
6.3.0 6 / 14
6.2.0 6 / 13
6.1.1 6 / 13
6.1.0 6 / 13
6.0.1 6 / 13
6.0.0 7 / 12
5.16.1 7 / 12
5.16.0 7 / 12
5.15.1 7 / 12
5.15.0 7 / 12
5.14.1 7 / 12
5.14.0 7 / 12
5.13.0 7 / 12
5.12.0 7 / 12
5.11.1 7 / 12
5.11.0 7 / 12
5.10.0 7 / 12
5.9.2 7 / 12
5.9.1 7 / 12
5.9.0 7 / 12
5.8.0 6 / 12
5.7.0 6 / 12
5.6.2 6 / 11
5.6.1 6 / 11
5.6.0 6 / 11
5.5.0 6 / 14
5.4.1 6 / 15
5.4.0 6 / 15
5.3.0 6 / 15
5.2.0 6 / 14
5.1.0 5 / 14
5.0.6 5 / 14
5.0.5 5 / 14
5.0.4 5 / 14
5.0.3 5 / 14
5.0.2 5 / 14
5.0.1 5 / 15
5.0.0 5 / 15
4.2.0 6 / 15
4.1.0 6 / 15
4.0.0 6 / 15
3.2.0 6 / 12
3.1.0 6 / 12
3.0.3 5 / 12
3.0.2 5 / 11
3.0.1 5 / 11
3.0.0 5 / 11
2.7.13 4 / 13
2.7.12 4 / 13
2.7.11 4 / 13
2.7.10 4 / 13
2.7.9 4 / 13
2.7.8 4 / 13
2.7.7 4 / 13
2.7.6 4 / 12
2.7.5 4 / 12
2.7.4 4 / 12
2.7.3 4 / 12
2.7.2 4 / 12
2.7.1 4 / 12
2.7.0 4 / 12
2.6.0 4 / 12
2.5.4 4 / 12
2.5.3 4 / 12
2.5.2 4 / 12
2.5.1 4 / 12
2.5.0 4 / 12
2.4.2 3 / 12
2.4.1 3 / 12
2.4.0 3 / 12
2.3.1 3 / 12
2.3.0 3 / 12
2.2.10 3 / 12
2.2.9 3 / 12
2.2.8 3 / 13
2.2.7 3 / 13
2.2.6 3 / 13
2.2.4 3 / 13
2.2.3 3 / 13
2.2.2 3 / 13
2.2.1 3 / 13
2.2.0 3 / 13
2.1.0 3 / 13
2.0.2 3 / 13
2.0.1 3 / 13
2.0.0 3 / 13
1.21.0 3 / 14
1.20.2 3 / 14
1.20.1 3 / 14
1.20.0 3 / 14
1.19.0 3 / 14
1.18.0 3 / 14
1.17.0 3 / 14
1.16.4 3 / 14
1.16.3 3 / 14
1.16.2 3 / 14
1.16.1 3 / 14
Showing 100 of 168 Next page →

v7.0.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: fdawgs → climba03003 (on 2026-07-09, known maintainer) provenance

This version was published by a different npm account (climba03003) than the most recent previously approved version (fdawgs) on 2026-07-09, but climba03003 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v7.0.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: matteo.collina → fdawgs (on 2026-06-09, known maintainer) provenance

This version was published by a different npm account (fdawgs) than the most recent previously approved version (matteo.collina) on 2026-06-09, but fdawgs is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v5.14.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.14.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.13.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.12.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.11.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.11.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.9.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.8.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.5.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.4.1

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: matteo.collina.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.6

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: matteo.collina → eomm (on 2022-07-05) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-05. This could indicate a legitimate maintainer transition or an account compromise.

v5.0.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v5.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.