@backstage/plugin-catalog-backend-module-bitbucket-server
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Official Backstage monorepo package; stable dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official Backstage monorepo package; stable dependency for all @backstage/* plugins. | ai | |
| dependencies | unvetted-dep:@backstage/integration | AI (dependencies): Official Backstage monorepo package; standard integration library for Backstage plugins. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Official Backstage monorepo package; core catalog model used across all catalog plugins. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official Backstage monorepo package; standard backend plugin API for all Backstage backend modules. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-events-node | AI (dependencies): Official Backstage monorepo package; events node library used across Backstage backend plugins. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): Official Backstage monorepo package; catalog node library used across Backstage catalog plugins. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-common | AI (dependencies): Official Backstage monorepo package; shared catalog types used across Backstage catalog plugins. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package; documentation lives in the main backstage/backstage repo. Short README and missing description are expected for sub-packages. | ai | |
| provenance | no-provenance | AI (provenance): Established package (1354 days, 1327 versions) predating widespread provenance adoption; absence is not a risk signal here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.5.11 | 8 / 4 | |
| 0.5.10 | 9 / 4 | |
| 0.5.9 | 9 / 4 | |
| 0.5.8 | 9 / 4 | |
| 0.5.7 | 9 / 4 | |
| 0.5.6 | 9 / 4 | |
| 0.5.5 | 9 / 4 | |
| 0.5.4 | 9 / 4 | |
| 0.5.3 | 10 / 5 | |
| 0.5.2 | 10 / 5 | |
| 0.5.1 | 10 / 5 | |
| 0.5.0 | 10 / 5 | |
| 0.4.1 | 10 / 5 |
v0.5.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.