@parsifal-m/plugin-opa-backend
The opa backend plugin responsible for interacting with the OPA server for validation and authorisation requests
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/catalog-client | AI (phantom-deps): Backstage framework dependency referenced in config; stable for this plugin. | ai | |
| phantom-deps | phantom-dep:knex | AI (phantom-deps): Database utility referenced in config; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Framework-scoped type package loaded by convention; stable. | ai | |
| phantom-deps | phantom-dep:@backstage/errors | AI (phantom-deps): Backstage framework package loaded by convention; stable. | ai | |
| phantom-deps | phantom-dep:yn | AI (phantom-deps): Utility loaded by convention in Backstage plugin; stable pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/catalog-model | AI (phantom-deps): Backstage framework package loaded by convention; stable. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-node | AI (phantom-deps): Backstage framework package loaded by convention; stable. | ai | |
| phantom-deps | phantom-dep:@backstage/integration | AI (phantom-deps): Backstage framework package loaded by convention; stable. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 15 / 5 | |
| 2.1.1 | 14 / 5 | |
| 2.1.0 | 14 / 5 | |
| 2.0.1 | 13 / 5 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.