@backstage/plugin-scaffolder-backend-module-rails
A module for the scaffolder backend that lets you template projects using Rails
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): First-party @backstage scoped package from the same official monorepo; unvetted status is a pipeline artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): First-party @backstage scoped package from the same official monorepo; unvetted status is a pipeline artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-scaffolder-node | AI (dependencies): First-party @backstage scoped package from the same official monorepo; unvetted status is a pipeline artifact, not a real risk. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org-scope package; phantom import pattern is expected in Backstage monorepo build output (type-only or transitive use). | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org-scope package; phantom import pattern is expected in Backstage monorepo build output (type-only or transitive use). | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.5.21 | 9 / 6 | |
| 0.5.20 | 9 / 6 | |
| 0.5.19 | 9 / 7 | |
| 0.5.18 | 9 / 7 | |
| 0.5.17 | 9 / 7 | |
| 0.5.16 | 9 / 7 | |
| 0.5.15 | 9 / 7 | |
| 0.5.14 | 9 / 7 | |
| 0.5.13 | 9 / 7 | |
| 0.5.12 | 9 / 7 | |
| 0.5.11 | 9 / 7 | |
| 0.5.10 | 9 / 7 | |
| 0.5.9 | 9 / 7 |
v0.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.