@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, so a manually published version cannot be tied back to a reviewed commit.
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 62 of 62)
| Version | Deps | Published |
|---|---|---|
| 0.5.13 | 8 / 4 | |
| 0.5.12 | 8 / 4 | |
| 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 | |
| 0.4.0 | 10 / 5 | |
| 0.3.3 | 8 / 4 | |
| 0.3.2 | 8 / 4 | |
| 0.3.1 | 8 / 4 | |
| 0.3.0 | 8 / 4 | |
| 0.2.4 | 9 / 4 | |
| 0.2.3 | 9 / 4 | |
| 0.2.2 | 9 / 4 | |
| 0.2.1 | 9 / 4 | |
| 0.2.0 | 9 / 4 | |
| 0.1.36 | 11 / 4 | |
| 0.1.35 | 11 / 4 | |
| 0.1.34 | 11 / 4 | |
| 0.1.33 | 11 / 4 | |
| 0.1.32 | 11 / 4 | |
| 0.1.31 | 11 / 4 | |
| 0.1.30 | 12 / 4 | |
| 0.1.29 | 12 / 4 | |
| 0.1.28 | 12 / 4 | |
| 0.1.27 | 12 / 4 | |
| 0.1.26 | 12 / 4 | |
| 0.1.25 | 12 / 4 | |
| 0.1.24 | 12 / 4 | |
| 0.1.23 | 12 / 4 | |
| 0.1.22 | 12 / 4 | |
| 0.1.21 | 12 / 4 | |
| 0.1.20 | 12 / 4 | |
| 0.1.19 | 12 / 4 | |
| 0.1.18 | 12 / 4 | |
| 0.1.17 | 12 / 4 | |
| 0.1.16 | 12 / 4 | |
| 0.1.15 | 12 / 4 | |
| 0.1.14 | 12 / 4 | |
| 0.1.13 | 12 / 4 | |
| 0.1.12 | 12 / 4 | |
| 0.1.11 | 12 / 4 | |
| 0.1.10 | 12 / 4 | |
| 0.1.9 | 12 / 4 | |
| 0.1.8 | 12 / 4 | |
| 0.1.7 | 13 / 4 | |
| 0.1.6 | 13 / 4 | |
| 0.1.5 | 13 / 4 | |
| 0.1.4 | 13 / 4 | |
| 0.1.3 | 13 / 4 | |
| 0.1.2 | 11 / 3 | |
| 0.1.1 | 11 / 3 | |
| 0.1.0 | 10 / 3 |
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
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.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.