node-plop
3
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
amwmediacrutchcorn
Keywords
plopgeneratorscaffoldingnodeprogrammaticautomation
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/picomatch | AI (phantom-deps): @types/picomatch is a type-declaration package used in node-plop's TypeScript definitions; same pattern as @types/inquirer — not a real phantom dep risk. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): The dynamic require loads the user's own package.json for project metadata — standard scaffolding tool behavior, not arbitrary/dangerous module loading. | ai | |
| phantom-deps | phantom-dep:@types/inquirer | AI (phantom-deps): @types/inquirer is a TypeScript type declaration package; its presence as a runtime dep is unusual but harmless for this package. | ai |
v0.32.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.1
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.26.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.