@backstage/plugin-scaffolder-backend-module-yeoman
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:winston | AI (phantom-deps): Winston is a standard logging dep in Backstage packages; phantom-dep heuristic fires false positives in monorepo builds where usage may be indirect or via config. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org @backstage scoped package; phantom-dep heuristic commonly fires false positives in Backstage monorepo packages. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-scaffolder-node-test-utils | AI (phantom-deps): Same-org @backstage scoped test utility; phantom-dep heuristic commonly fires false positives in Backstage monorepo packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo packages commonly omit descriptions; not a security signal for this established package. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage package predating widespread Sigstore adoption; absence of provenance is not a risk signal here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.4.22 | 6 / 1 | |
| 0.4.21 | 7 / 1 | |
| 0.4.20 | 7 / 1 | |
| 0.4.19 | 7 / 1 | |
| 0.4.18 | 7 / 1 | |
| 0.4.17 | 7 / 1 | |
| 0.4.16 | 7 / 1 | |
| 0.4.15 | 7 / 1 | |
| 0.4.14 | 7 / 1 | |
| 0.4.13 | 7 / 1 | |
| 0.4.12 | 7 / 1 | |
| 0.4.11 | 7 / 1 | |
| 0.4.10 | 7 / 1 |
v0.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
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.4.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.4.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.4.16
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.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.13
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.4.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.4.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.4.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.