stringify-keys
Build an array of key paths from an object.
9
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
doowbjonschlinkert
Keywords
dotkeysnestednotationobjectpathpathsrecurserecursiveseparatorstringify
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): jonschlinkert is a listed contributor and one of the most trusted npm publishers; the 2019 transition from doowb is a legitimate known-collaborator handoff, not a takeover. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 3 | |
| 2.0.0 | 1 / 2 | |
| 1.0.1 | 1 / 2 | |
| 1.0.0 | 1 / 2 | |
| 0.3.0 | 1 / 2 | |
| 0.2.0 | 1 / 2 | |
| 0.1.2 | 0 / 2 | |
| 0.1.1 | 0 / 2 | |
| 0.1.0 | 0 / 2 |
v3.0.0
2 findings
HIGH
Publisher changed: doowb → jonschlinkert (on 2019-01-22)
provenance
This version was published by a different npm account than previous versions on 2019-01-22. 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.
v2.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.