@pagerduty/backstage-plugin-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@backstage/plugin-scaffolder-node | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@rjsf/core | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@material-ui/core | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-tasks | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-model | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/core-plugin-api | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-defaults | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-node | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-common | AI (phantom-deps): Backstage plugin config-schema reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is a type-only dev/peer dep commonly listed in dependencies for Backstage plugins; not a real phantom dep concern. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 12 / 5 | |
| 0.10.2 | 11 / 5 | |
| 0.10.1 | 23 / 4 | |
| 0.9.11 | 23 / 4 | |
| 0.9.10 | 23 / 4 | |
| 0.9.9 | 23 / 4 | |
| 0.9.8 | 23 / 4 | |
| 0.9.7 | 23 / 4 | |
| 0.9.6 | 23 / 12 |
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.