@backstage/plugin-scaffolder-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Backstage monorepo sub-packages consistently have minimal standalone READMEs and no keywords; this is a structural pattern, not a spam indicator. | ai | |
| provenance | no-provenance | AI (provenance): Established official Backstage package with 754 versions and 56k weekly downloads; lack of Sigstore provenance is not a risk signal here. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 0.2.23 | 7 / 4 | |
| 0.2.22 | 7 / 4 | |
| 0.2.21 | 7 / 4 | |
| 0.2.20 | 7 / 4 | |
| 0.2.19 | 7 / 4 | |
| 0.2.18 | 7 / 4 | |
| 0.2.17 | 7 / 4 | |
| 0.2.16 | 7 / 4 | |
| 0.2.15 | 7 / 4 | |
| 0.2.14 | 7 / 4 | |
| 0.2.13 | 8 / 4 | |
| 0.2.12 | 8 / 4 | |
| 0.2.11 | 8 / 4 | |
| 0.2.10 | 8 / 4 | |
| 0.2.9 | 7 / 4 | |
| 0.2.8 | 7 / 4 | |
| 0.2.7 | 7 / 4 | |
| 0.2.6 | 7 / 4 | |
| 0.2.5 | 7 / 4 | |
| 0.2.4 | 7 / 4 | |
| 0.2.3 | 8 / 4 | |
| 0.2.2 | 8 / 4 | |
| 0.2.1 | 8 / 4 | |
| 0.2.0 | 8 / 4 | |
| 0.1.14 | 8 / 4 | |
| 0.1.13 | 8 / 4 | |
| 0.1.12 | 8 / 4 | |
| 0.1.11 | 8 / 4 | |
| 0.1.10 | 8 / 4 | |
| 0.1.9 | 8 / 4 | |
| 0.1.8 | 8 / 4 | |
| 0.1.7 | 8 / 4 |
v0.2.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
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.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.