@pagerduty/backstage-plugin-entity-processor
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/backend-defaults | AI (phantom-deps): Config-referenced dependency; stable pattern for Backstage plugins. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Config-referenced dependency; stable pattern for Backstage plugins. | ai | |
| phantom-deps | phantom-dep:@rjsf/core | AI (phantom-deps): Config-referenced dependency; stable pattern for Backstage plugins. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-common | AI (phantom-deps): Config-referenced dependency; stable pattern for Backstage plugins. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Config-referenced dependency; stable pattern for Backstage plugins. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Config-referenced dependency; stable pattern for Backstage plugins. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-common | AI (phantom-deps): Config-referenced dependency; stable pattern for Backstage plugins. | ai | |
| phantom-deps | phantom-dep:winston | AI (phantom-deps): Config-referenced dependency; stable pattern for Backstage plugins. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.3.10 | 8 / 1 | |
| 0.3.7 | 8 / 1 | |
| 0.3.6 | 13 / 1 | |
| 0.3.5 | 13 / 1 | |
| 0.3.4 | 13 / 1 | |
| 0.3.3 | 13 / 1 |
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.