node-machine
Please `npm install machine` instead.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:mikermcneil | AI (email-domain): The author field uses '@mikermcneil' as a Twitter handle, not an actual email address. No real email domain is at risk of being claimed. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is the core functionality of Machine.pack.js — it loads machine definitions from a configured directory. This is expected and documented behavior for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Package has a docs URL (node-machine.org), is 4349 days old with 19 versions, and the empty index.js is a common re-export pattern. Bogus signals are false positives for this established package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 1 / 2 | |
| 2.0.0 | 1 / 2 | |
| 1.0.1 | 5 / 2 | |
| 1.0.0 | 5 / 2 | |
| 0.3.0 | 4 / 1 | |
| 0.2.4 | 4 / 1 | |
| 0.2.3 | 4 / 1 | |
| 0.2.2 | 4 / 1 | |
| 0.2.1 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.4 | 4 / 0 | |
| 0.1.2 | 4 / 0 | |
| 0.1.1 | 4 / 0 | |
| 0.1.0 | 4 / 0 | |
| 0.0.5 | 4 / 0 | |
| 0.0.4 | 4 / 0 | |
| 0.0.3 | 3 / 0 | |
| 0.0.2 | 2 / 0 | |
| 0.0.1 | 2 / 0 |
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
2 findingsMaintainer email '@mikermcneil' uses domain 'mikermcneil' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
2 findingsMaintainer email '@mikermcneil' uses domain 'mikermcneil' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.