@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, so a manually published version cannot be tied back to a reviewed commit.
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 78 of 78)
| Version | Deps | Published |
|---|---|---|
| 0.4.24 | 6 / 1 | |
| 0.4.23 | 6 / 1 | |
| 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 | |
| 0.4.9 | 7 / 1 | |
| 0.4.8 | 7 / 1 | |
| 0.4.7 | 7 / 1 | |
| 0.4.6 | 7 / 1 | |
| 0.4.5 | 7 / 1 | |
| 0.4.4 | 7 / 1 | |
| 0.4.3 | 7 / 1 | |
| 0.4.2 | 7 / 2 | |
| 0.4.1 | 7 / 2 | |
| 0.4.0 | 7 / 2 | |
| 0.3.8 | 7 / 2 | |
| 0.3.7 | 7 / 2 | |
| 0.3.6 | 7 / 2 | |
| 0.3.5 | 7 / 2 | |
| 0.3.4 | 7 / 2 | |
| 0.3.3 | 7 / 2 | |
| 0.3.2 | 7 / 2 | |
| 0.3.1 | 7 / 2 | |
| 0.3.0 | 7 / 2 | |
| 0.2.37 | 6 / 2 | |
| 0.2.36 | 6 / 2 | |
| 0.2.35 | 6 / 2 | |
| 0.2.34 | 5 / 2 | |
| 0.2.33 | 5 / 2 | |
| 0.2.32 | 5 / 2 | |
| 0.2.31 | 5 / 2 | |
| 0.2.30 | 4 / 2 | |
| 0.2.29 | 5 / 2 | |
| 0.2.28 | 5 / 2 | |
| 0.2.27 | 5 / 2 | |
| 0.2.26 | 5 / 2 | |
| 0.2.25 | 5 / 2 | |
| 0.2.24 | 5 / 2 | |
| 0.2.23 | 5 / 2 | |
| 0.2.22 | 5 / 2 | |
| 0.2.21 | 5 / 2 | |
| 0.2.20 | 5 / 2 | |
| 0.2.19 | 5 / 2 | |
| 0.2.18 | 5 / 2 | |
| 0.2.17 | 5 / 2 | |
| 0.2.16 | 5 / 2 | |
| 0.2.15 | 5 / 2 | |
| 0.2.14 | 5 / 2 | |
| 0.2.13 | 5 / 2 | |
| 0.2.12 | 5 / 2 | |
| 0.2.11 | 5 / 2 | |
| 0.2.10 | 5 / 2 | |
| 0.2.9 | 5 / 2 | |
| 0.2.8 | 5 / 2 | |
| 0.2.7 | 5 / 2 | |
| 0.2.6 | 5 / 2 | |
| 0.2.5 | 5 / 2 | |
| 0.2.4 | 5 / 2 | |
| 0.2.3 | 5 / 2 | |
| 0.2.2 | 5 / 2 | |
| 0.2.1 | 5 / 2 | |
| 0.2.0 | 5 / 2 | |
| 0.1.5 | 5 / 2 | |
| 0.1.4 | 5 / 2 | |
| 0.1.3 | 5 / 2 | |
| 0.1.2 | 5 / 2 | |
| 0.1.1 | 5 / 2 | |
| 0.1.0 | 4 / 2 |
v0.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
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.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.