@types/fast-json-stable-stringify
Stub TypeScript definitions entry for fast-json-stable-stringify, which provides its own types definitions
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): Adding the underlying package as a runtime dep is the standard DefinitelyTyped stub pattern when the package ships its own types. Stable and expected for this @types/ package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): This is a legitimate DefinitelyTyped stub package. No README code, no repo link, no keywords, and tiny payload are all expected characteristics of a stub types redirect package. | ai | |
| phantom-deps | phantom-dep:fast-json-stable-stringify | AI (phantom-deps): Stub package has no code to import the dependency; the dep declaration is intentional to pull in the real package's types. | ai | |
| dependencies | unvetted-dep:fast-json-stable-stringify | AI (dependencies): Dependency on fast-json-stable-stringify is the entire purpose of this stub package; stable and expected for all versions. | ai |
v2.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.