whelk
Run a JavaScript function as a shell script.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate maintainer transition within sailshq org from mikermcneil to eashaw, a trusted publisher with 856 approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): eashaw is a known Sails.js ecosystem maintainer with extensive track record; legitimate org handoff. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by org-level maintenance transition; no code changes in this publish. | ai | |
| typosquat | typosquat.levenshtein:chalk | AI (typosquat): whelk is a legitimate, 8+ year old package in the Sails.js ecosystem. It actually depends on chalk. The Levenshtein match is purely mechanical with no typosquat intent. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 6.0.2 | 7 / 3 | |
| 6.0.1 | 7 / 3 | |
| 6.0.0 | 7 / 3 | |
| 5.2.0 | 7 / 3 | |
| 5.1.0 | 7 / 3 | |
| 5.0.3 | 7 / 3 | |
| 5.0.2 | 7 / 3 | |
| 5.0.1 | 7 / 3 | |
| 5.0.0 | 7 / 3 |
v6.0.2
2 findingsThis version was published by a different npm account than previous versions on 2024-03-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.