@pagerduty/backstage-plugin-scaffolder-actions
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Backstage plugin with clear purpose in package.json metadata; description omission is benign. | ai | |
| phantom-deps | phantom-dep:@rjsf/utils | AI (phantom-deps): Config-file reference in Backstage plugin; stable pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-defaults | AI (phantom-deps): Config-file reference in Backstage plugin; stable pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-test-utils | AI (phantom-deps): Config-file reference in Backstage plugin; stable pattern. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Config-file reference in Backstage plugin; stable pattern. | ai | |
| phantom-deps | phantom-dep:@rjsf/core | AI (phantom-deps): Config-file reference in Backstage plugin; stable pattern. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Logging dep used indirectly via Backstage backend-common; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Config dep referenced in config.d.ts schema; stable false positive for this Backstage plugin. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): Backstage plugin pattern; react declared as peer/runtime dep, used indirectly via framework. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.2.9 | 8 / 5 | |
| 0.2.7 | 8 / 5 | |
| 0.2.6 | 8 / 5 | |
| 0.2.5 | 14 / 3 | |
| 0.2.4 | 14 / 3 | |
| 0.2.3 | 14 / 3 |
v0.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.