node-plop No license 46 versions

node-plop

npm Repository Homepage

46

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

amwmediacrutchcorn

Keywords

plopgeneratorscaffoldingnodeprogrammaticautomation

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed-stale	AI (provenance): Stable for 2330+ days, consistent with legitimate maintainer handoff, not takeover.	ai	2026/07/20
phantom-deps	phantom-dep:@types/globby	AI (phantom-deps): Types package loaded by convention, not directly imported.	ai	2026/07/20
dependencies	unvetted-dep:@types/globby	AI (dependencies): Type-only stub package, no runtime behavior risk.	ai	2026/07/20
phantom-deps	phantom-dep:@types/handlebars	AI (phantom-deps): Types package loaded by convention, not directly imported.	ai	2026/07/20
publish-pattern	new-deps-added	AI (publish-pattern): dlv is a tiny well-known utility replacing lodash.get; part of a dependency cleanup.	ai	2026/07/07
publish-pattern	dormant-publish	AI (publish-pattern): Established maintainer with strong track record; gap reflects normal maintenance cadence, not takeover.	ai	2026/07/07
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	2026/04/25
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	2026/04/25
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	2026/04/25

Versions (showing 46 of 46)

Version	Deps	Published
0.32.3	10 / 6	2025-09-26
0.32.2	9 / 6	2025-09-20
0.32.1	11 / 6	2025-09-04
0.32.0	13 / 6	2023-09-05
0.31.1	13 / 6	2023-02-08
0.31.0	13 / 6	2022-04-27
0.30.1	13 / 6	2022-04-25
0.30.0	13 / 11	2021-11-27
0.26.3	11 / 20	2021-10-18
0.26.2	11 / 20	2020-07-31
0.26.1	11 / 20	2020-07-19
0.26.0	11 / 20	2020-05-21
0.25.0	13 / 17	2020-03-03
0.24.0	14 / 14	2020-02-17
0.23.0	14 / 14	2019-11-04
0.22.0	14 / 14	2019-10-18
0.21.0	14 / 14	2019-10-18
0.20.0	14 / 14	2019-10-16
0.19.0	12 / 17	2019-06-19
0.18.0	12 / 17	2019-02-27
0.17.4	12 / 15	2019-02-18
0.17.3	12 / 13	2018-12-14
0.17.2	13 / 13	2018-12-13
0.17.1	13 / 13	2018-12-13
0.17.0	13 / 13	2018-12-13
0.16.0	13 / 13	2018-08-03
0.15.0	13 / 12	2018-06-06
0.13.0	12 / 13	2018-03-05
0.12.0	12 / 13	2018-03-05
0.9.0	12 / 11	2017-10-02
0.8.0	12 / 11	2017-09-22
0.7.1	12 / 11	2017-08-23
0.7.0	12 / 11	2017-06-01
0.6.0	12 / 11	2017-05-11
0.5.5	11 / 10	2017-01-26
0.5.4	9 / 10	2016-12-06
0.5.3	9 / 10	2016-11-28
0.5.2	9 / 10	2016-11-21
0.5.1	9 / 10	2016-11-18
0.5.0	9 / 10	2016-11-17
0.4.2	9 / 23	2016-11-04
0.4.1	9 / 23	2016-11-04
0.4.0	9 / 23	2016-11-04
0.3.0	9 / 22	2016-11-01
0.2.0	7 / 3	2016-10-24
0.0.1	7 / 3	2016-10-06

v0.32.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.32.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.31.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.31.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.30.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.26.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.26.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.0

2 findings

MEDIUM Publisher changed: amwmedia → crutchcorn (on 2020-05-21, unremoved on npm for 2251d) provenance

This version was published by a different npm account (crutchcorn) than the most recent previously approved version (amwmedia) on 2020-05-21. It has since remained available on npm for 2251 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.25.0

2 findings

MEDIUM Publisher changed: amwmedia → crutchcorn (on 2020-03-03, unremoved on npm for 2330d) provenance

This version was published by a different npm account (crutchcorn) than the most recent previously approved version (amwmedia) on 2020-03-03. It has since remained available on npm for 2330 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.24.0

2 findings

MEDIUM Publisher changed: amwmedia → crutchcorn (on 2020-02-17, unremoved on npm for 2344d) provenance

This version was published by a different npm account (crutchcorn) than the most recent previously approved version (amwmedia) on 2020-02-17. It has since remained available on npm for 2344 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.22.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.21.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.20.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.19.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

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.0.1

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.