← Home

toidentifier

npm Repository Homepage

Convert a string of words to a JavaScript identifier

3
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

niftylettucedougwilsonjongleberry

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate transfer from original author (niftylettuce) to primary maintainer (dougwilson) who is listed as package author and has extensive npm track record. ai
maintainer-change maintainer-added AI (maintainer-change): dougwilson and jongleberry are known Express ecosystem maintainers; legitimate maintainer addition. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance; no provenance is expected for packages published in 2018. ai

Versions (showing 3 of 3)

Version Deps Published
1.0.1 0 / 9
1.0.0 0 / 9
0.0.1 0 / 15

v1.0.0

2 findings
HIGH Publisher changed: niftylettuce → dougwilson (on 2018-07-09) provenance

This version was published by a different npm account than previous versions on 2018-07-09. 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.

v0.0.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.