fast-json-stringify — Greenflagged

Stringify your JSON at max speed

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.

Source	Rule	Reason	Accepted by	When
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	2026/04/23
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	2026/04/23
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	2026/04/23

Versions (showing 51 of 166)

View all versions

Version	Deps	Published
6.4.0	6 / 14	2026-05-05
6.3.0	6 / 14	2026-02-06
6.2.0	6 / 13	2026-01-15
6.1.1	6 / 13	2025-09-29
6.1.0	6 / 13	2025-09-28
6.0.1	6 / 13	2025-01-16
6.0.0	7 / 12	2024-06-21
5.16.1	7 / 12	2024-06-19
5.16.0	7 / 12	2024-05-22
5.15.1	7 / 12	2024-05-06
5.15.0	7 / 12	2024-04-24
5.14.1	7 / 12	2024-04-10
5.14.0	7 / 12	2024-04-09
5.13.0	7 / 12	2024-03-12
5.12.0	7 / 12	2024-02-05
5.11.1	7 / 12	2024-02-01
5.11.0	7 / 12	2024-02-01
5.10.0	7 / 12	2024-01-06
5.9.2	7 / 12	2023-12-26
5.9.1	7 / 12	2023-11-03
5.9.0	7 / 12	2023-11-02
5.8.0	6 / 12	2023-08-02
5.7.0	6 / 12	2023-04-02
5.6.2	6 / 11	2023-02-23
5.6.1	6 / 11	2023-02-22
5.6.0	6 / 11	2023-02-21
5.5.0	6 / 14	2022-12-05
5.4.1	6 / 15	2022-11-07
5.4.0	6 / 15	2022-09-26
5.3.0	6 / 15	2022-09-09
5.2.0	6 / 14	2022-08-31
5.1.0	5 / 14	2022-07-11
5.0.6	5 / 14	2022-07-05
5.0.5	5 / 14	2022-06-29
5.0.4	5 / 14	2022-06-29
5.0.3	5 / 14	2022-06-28
5.0.2	5 / 14	2022-06-27
5.0.1	5 / 15	2022-06-23
5.0.0	5 / 15	2022-06-22
4.2.0	6 / 15	2022-06-13
4.1.0	6 / 15	2022-06-10
4.0.0	6 / 15	2022-06-05
3.2.0	6 / 12	2022-05-04
3.1.0	6 / 12	2022-04-17
3.0.3	5 / 12	2022-02-11
3.0.2	5 / 11	2022-01-18
3.0.1	5 / 11	2022-01-17
3.0.0	5 / 11	2022-01-03
2.7.13	4 / 13	2021-12-23
2.7.12	4 / 13	2021-11-10
2.7.11	4 / 13	2021-10-19

v6.4.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: climba03003 → matteo.collina (on 2026-05-05) provenance

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

v6.3.0

2 findings

HIGH Publisher changed: eomm → climba03003 (on 2026-02-06) provenance

This version was published by a different npm account than previous versions on 2026-02-06. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v6.2.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 → eomm (on 2026-01-15) provenance

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

v6.1.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: eomm → matteo.collina (on 2025-09-29) provenance

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

v6.1.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: fdawgs → eomm (on 2025-09-28) provenance

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

v6.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: jsumners → fdawgs (on 2025-01-16) provenance

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

v6.0.0

1 finding

LOW No provenance attestation provenance

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

v5.16.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: matteo.collina → jsumners (on 2024-06-19) provenance

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

v5.16.0

1 finding

LOW No provenance attestation provenance

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

v5.15.1

1 finding

LOW No provenance attestation provenance

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

v5.15.0

1 finding

LOW No provenance attestation provenance

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

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.