switchback
Normalize callback fns to switchbacks and vice versa
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): rachaelshaw is a known Sails.js core team member with 754 approved packages; this is a legitimate team transition within the node-machine/Sails ecosystem. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of sgress454, particlebanana, irl is consistent with Sails.js team reorganization; no evidence of hostile takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @sailshq/lodash is the Sails.js team's own lodash fork, a direct replacement for lodash; not a suspicious third-party dependency. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from sgress454 to mikermcneil is a documented, legitimate handoff between two core Sails.js maintainers in 2016. Both are part of the same organization; this is stable for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 2.0.5 | 1 / 2 | |
| 2.0.4 | 1 / 2 | |
| 2.0.2 | 1 / 2 | |
| 2.0.1 | 1 / 2 | |
| 2.0.0 | 1 / 2 | |
| 1.1.3 | 1 / 2 | |
| 1.1.2 | 1 / 2 | |
| 1.1.1 | 1 / 2 | |
| 1.1.0 | 1 / 2 | |
| 1.0.1 | 1 / 2 | |
| 1.0.0 | 1 / 2 | |
| 0.2.0 | 0 / 0 | |
| 0.0.1 | 0 / 0 |
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-04-15. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.2
2 findingsThis version was published by a different npm account than previous versions on 2016-10-07. 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.
v2.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2016-05-03. This could indicate a legitimate maintainer transition or an account compromise.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2015-02-08. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-11-13. This could indicate a legitimate maintainer transition or an account compromise.