safe-stable-stringify MIT 10 versions

safe-stable-stringify

npm Repository Homepage

Deterministic and safely JSON.stringify to quickly serialize JavaScript objects

10

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

bridgear

Keywords

stablestringifyJSONJSON.stringifysafeserializedeterministiccircularobjectpredicablerepeatablefastbigint

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:dynamic-require	AI (semgrep): Benchmark/compare script loading known dev-dependency stringify libs, not runtime code.	ai	2026/07/19

Versions (showing 10 of 10)

Version	Deps	Published
2.5.0	0 / 15	2024-08-24
2.4.3	0 / 15	2023-03-19
2.4.2	0 / 15	2022-12-28
2.4.1	0 / 15	2022-10-18
2.4.0	0 / 15	2022-09-17
2.3.1	0 / 15	2021-12-04
2.3.0	0 / 15	2021-11-29
2.2.0	0 / 14	2021-10-31
2.1.0	0 / 14	2021-10-19
2.0.0	0 / 12	2021-09-19

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.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.

v2.1.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.

v2.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.