@red-hat-developer-hub/backstage-plugin-scaffolder-backend-module-orchestrator
The orchestrator module for @backstage/plugin-scaffolder-backend
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Backstage plugin module pattern; declared for type resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-model | AI (phantom-deps): Backstage plugin module pattern; declared for type resolution, not direct import. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-permission-common | AI (phantom-deps): Backstage plugin module pattern; declared for type resolution, not direct import. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.5.3 | 8 / 5 | |
| 1.5.2 | 8 / 5 | |
| 1.5.1 | 8 / 5 | |
| 1.5.0 | 8 / 5 | |
| 1.4.3 | 8 / 5 | |
| 1.4.2 | 8 / 5 | |
| 1.4.1 | 8 / 5 | |
| 1.4.0 | 8 / 5 | |
| 1.3.6 | 8 / 5 | |
| 1.3.5 | 8 / 5 | |
| 1.3.4 | 8 / 5 | |
| 1.3.3 | 8 / 5 | |
| 1.3.2 | 8 / 5 | |
| 1.3.1 | 8 / 5 | |
| 1.3.0 | 8 / 4 | |
| 1.2.0 | 8 / 4 | |
| 1.1.0 | 8 / 4 | |
| 1.0.6 | 8 / 4 | |
| 1.0.5 | 8 / 4 | |
| 1.0.4 | 8 / 4 | |
| 1.0.3 | 8 / 4 | |
| 1.0.2 | 8 / 4 | |
| 1.0.1 | 8 / 4 | |
| 1.0.0 | 8 / 4 |
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.