machinepack-strings
Work with strings.
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): sgress454 and mikermcneil are both Sails.js core team members; this is a legitimate intra-org maintainer transition, not a suspicious takeover. | ai | |
| phantom-deps | phantom-dep:browserify-transform-machinepack | AI (phantom-deps): browserify-transform-machinepack is a browserify transform declared in the browserify config field; it is not directly require()d in source, making this a stable false positive for this package. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 6.1.2 | 3 / 3 | |
| 6.1.1 | 4 / 3 | |
| 6.1.0 | 4 / 3 | |
| 6.0.2 | 4 / 3 | |
| 6.0.1 | 4 / 3 | |
| 6.0.0 | 4 / 3 | |
| 5.1.0 | 4 / 1 | |
| 5.0.0 | 4 / 1 | |
| 4.3.0 | 4 / 1 | |
| 4.2.0 | 4 / 1 | |
| 4.1.3 | 3 / 1 | |
| 4.1.2 | 3 / 1 | |
| 4.1.1 | 3 / 1 | |
| 4.1.0 | 3 / 1 | |
| 4.0.0 | 3 / 1 | |
| 3.1.1 | 3 / 1 | |
| 3.1.0 | 3 / 1 | |
| 3.0.0 | 3 / 1 | |
| 2.3.2 | 3 / 1 | |
| 2.3.0 | 3 / 1 | |
| 2.2.0 | 3 / 1 | |
| 2.1.0 | 3 / 1 | |
| 2.0.0 | 3 / 1 |
v6.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 2026-05-28. This could indicate a legitimate maintainer transition or an account compromise.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage 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
2 findingsThis version was published by a different npm account than previous versions on 2017-11-26. 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.
v5.1.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 2016-07-13. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.