machine-as-action
Run a machine from an HTTP or WebSocket request.
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): Publisher change from sgress454 to mikermcneil occurred in 2017; mikermcneil is the package author and Sails.js founder — a legitimate and long-standing transition. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 10.3.1 | 5 / 3 | |
| 10.3.0 | 5 / 3 | |
| 10.2.0 | 5 / 3 | |
| 10.1.1 | 5 / 3 | |
| 10.1.0 | 5 / 3 | |
| 9.0.2 | 5 / 3 | |
| 9.0.1 | 5 / 2 | |
| 9.0.0 | 5 / 2 | |
| 8.1.0 | 5 / 2 | |
| 8.0.2 | 5 / 2 | |
| 8.0.1 | 5 / 2 | |
| 8.0.0 | 5 / 2 | |
| 7.0.11 | 4 / 2 | |
| 7.0.10 | 4 / 2 | |
| 7.0.7 | 4 / 2 | |
| 7.0.6 | 4 / 2 | |
| 7.0.5 | 4 / 2 | |
| 7.0.4 | 4 / 2 | |
| 7.0.3 | 4 / 2 | |
| 7.0.2 | 4 / 2 | |
| 7.0.1 | 4 / 2 | |
| 7.0.0 | 4 / 2 | |
| 6.1.3 | 4 / 2 | |
| 6.1.2 | 4 / 2 | |
| 6.1.1 | 4 / 2 | |
| 6.1.0 | 4 / 2 | |
| 6.0.1 | 4 / 2 | |
| 6.0.0 | 4 / 2 | |
| 5.2.0 | 4 / 2 | |
| 5.0.1 | 4 / 2 | |
| 5.0.0 | 4 / 2 | |
| 4.1.2 | 4 / 2 | |
| 4.1.1 | 4 / 2 | |
| 4.1.0 | 4 / 2 | |
| 4.0.0 | 4 / 2 | |
| 3.1.0 | 4 / 2 | |
| 3.0.0 | 4 / 2 | |
| 2.0.8 | 2 / 2 | |
| 2.0.7 | 2 / 2 | |
| 2.0.6 | 2 / 2 | |
| 2.0.5 | 2 / 2 | |
| 2.0.4 | 2 / 2 | |
| 2.0.3 | 2 / 2 | |
| 2.0.2 | 2 / 2 | |
| 2.0.1 | 2 / 2 | |
| 2.0.0 | 2 / 2 | |
| 1.3.0 | 2 / 1 | |
| 1.2.0 | 2 / 1 | |
| 1.1.1 | 2 / 1 | |
| 1.1.0 | 2 / 1 |
v10.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
2 findingsThis version was published by a different npm account than previous versions on 2017-05-25. 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.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.