@types/json-stable-stringify MIT 11 versions

@types/json-stable-stringify

npm

Stub TypeScript definitions entry for json-stable-stringify, which provides its own types definitions

11

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

types

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
email-domain	unclaimed-email:https://github.com/mhfrantz/	AI (email-domain): DT author field uses profile URL not email; not a real domain hijack risk.	ai	2026/07/24
bogus-package	bogus-package	AI (bogus-package): Intentional DefinitelyTyped stub package; minimal payload and sparse metadata are by design.	ai	2026/04/29
phantom-deps	phantom-dep:json-stable-stringify	AI (phantom-deps): Stub types package; dependency is declared for peer resolution, not direct import — expected pattern.	ai	2026/04/29

Versions (showing 11 of 11)

Version	Deps	Published
1.2.0	1 / 0	2025-01-28
1.1.0	0 / 0	2024-10-24
1.0.36	0 / 0	2023-11-07
1.0.35	0 / 0	2023-10-18
1.0.34	0 / 0	2022-03-02
1.0.33	0 / 0	2021-07-06
1.0.32	0 / 0	2017-08-21
1.0.31	0 / 0	2017-03-31
1.0.30	0 / 0	2017-02-23
1.0.29	0 / 0	2016-09-19
1.0.28	0 / 0	2016-07-14

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

v1.0.36

1 finding

LOW No provenance attestation provenance

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

v1.0.35

1 finding

LOW No provenance attestation provenance

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

v1.0.34

1 finding

LOW No provenance attestation provenance

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

v1.0.33

1 finding

LOW No provenance attestation provenance

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

v1.0.32

1 finding

LOW No provenance attestation provenance

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

v1.0.31

1 finding

LOW No provenance attestation provenance

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

v1.0.30

1 finding

LOW No provenance attestation provenance

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

v1.0.29

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

2 findings

HIGH Unclaimed maintainer email domain: https://github.com/mhfrantz/ email-domain

Maintainer email 'https://github.com/mhfrantz/' uses domain 'https://github.com/mhfrantz/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

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.