@backstage/plugin-scaffolder-backend-module-cookiecutter
A module for the scaffolder backend that lets you template projects using cookiecutter
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yn | AI (phantom-deps): yn is a declared dependency referenced in config files; phantom dep finding is a stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): First-party @backstage org package; phantom dep pattern is expected in Backstage monorepo packages where deps may be used transitively or in config. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): First-party @backstage org package; phantom dep pattern is expected in Backstage monorepo packages. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-defaults | AI (phantom-deps): First-party @backstage org package; phantom dep pattern is expected in Backstage monorepo packages. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): winston is a declared dependency used in config/logging context; phantom dep finding is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Official Backstage monorepo package; lack of Sigstore provenance is common and not a risk signal given the package's established history and ecosystem trust. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.3.23 | 8 / 5 | |
| 0.3.22 | 12 / 5 | |
| 0.3.21 | 12 / 5 | |
| 0.3.20 | 12 / 5 | |
| 0.3.19 | 12 / 5 | |
| 0.3.18 | 12 / 5 | |
| 0.3.17 | 12 / 5 | |
| 0.3.16 | 12 / 5 | |
| 0.3.15 | 12 / 5 | |
| 0.3.14 | 12 / 5 | |
| 0.3.13 | 12 / 5 | |
| 0.3.12 | 12 / 5 | |
| 0.3.11 | 12 / 5 | |
| 0.3.10 | 12 / 5 |
v0.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.