@backstage/plugin-scaffolder-node-test-utils
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): First-party @backstage monorepo dependency; same org scope as this package, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): First-party @backstage monorepo dependency; same org scope as this package, not a third-party risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-scaffolder-node | AI (dependencies): First-party @backstage monorepo dependency; same org scope as this package, not a third-party risk. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-plugin-api | AI (phantom-deps): Same-org @backstage dependency; phantom usage is common in monorepo packages with type-only or transitive imports. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.3.13 | 6 / 5 | |
| 0.3.12 | 6 / 5 | |
| 0.3.11 | 6 / 5 | |
| 0.3.10 | 6 / 5 | |
| 0.3.9 | 6 / 5 | |
| 0.3.8 | 6 / 5 | |
| 0.3.7 | 6 / 5 | |
| 0.3.6 | 6 / 5 | |
| 0.3.5 | 6 / 5 | |
| 0.3.4 | 6 / 5 | |
| 0.3.3 | 6 / 5 | |
| 0.3.2 | 6 / 5 | |
| 0.3.1 | 6 / 5 | |
| 0.3.0 | 6 / 5 | |
| 0.2.2 | 6 / 5 | |
| 0.2.1 | 6 / 5 | |
| 0.2.0 | 6 / 5 | |
| 0.1.19 | 4 / 5 | |
| 0.1.18 | 4 / 5 | |
| 0.1.17 | 4 / 5 | |
| 0.1.16 | 4 / 5 | |
| 0.1.15 | 4 / 5 | |
| 0.1.14 | 4 / 5 | |
| 0.1.13 | 4 / 5 | |
| 0.1.12 | 4 / 2 | |
| 0.1.11 | 4 / 2 | |
| 0.1.10 | 4 / 2 | |
| 0.1.9 | 4 / 2 | |
| 0.1.8 | 4 / 2 | |
| 0.1.7 | 4 / 2 | |
| 0.1.6 | 4 / 2 | |
| 0.1.5 | 4 / 2 | |
| 0.1.4 | 4 / 2 | |
| 0.1.3 | 4 / 2 | |
| 0.1.2 | 4 / 2 | |
| 0.1.1 | 4 / 2 | |
| 0.1.0 | 4 / 2 |
v0.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.