@backstage/plugin-events-backend-module-bitbucket-server
15
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
patrikofrebenmarcuseide
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Backstage monorepo packages commonly omit descriptions in package.json; not a risk signal for this well-established plugin namespace. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo does not currently publish with Sigstore provenance attestations; consistent across all @backstage/* packages. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 0.1.14 | 2 / 3 | |
| 0.1.13 | 2 / 3 | |
| 0.1.12 | 2 / 3 | |
| 0.1.11 | 2 / 3 | |
| 0.1.10 | 2 / 3 | |
| 0.1.9 | 2 / 3 | |
| 0.1.8 | 2 / 3 | |
| 0.1.7 | 2 / 3 | |
| 0.1.6 | 2 / 3 | |
| 0.1.5 | 2 / 3 | |
| 0.1.4 | 2 / 3 | |
| 0.1.3 | 2 / 3 | |
| 0.1.2 | 2 / 3 | |
| 0.1.1 | 2 / 3 | |
| 0.1.0 | 2 / 3 |
v0.1.14
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.