@backstage/plugin-events-backend
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Official Backstage monorepo package; missing description is a known pattern in their published packages and not a malice indicator. | ai | |
| provenance | no-provenance | AI (provenance): Backstage publishes from their monorepo CI without Sigstore provenance; consistent across all their packages and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): @types/express is a TypeScript type package listed as a runtime dep for type augmentation; standard pattern in Express-based packages. | ai |
Versions (showing 51 of 62)
| Version | Deps | Published |
|---|---|---|
| 0.6.4 | 11 / 8 | |
| 0.6.3 | 11 / 8 | |
| 0.6.2 | 11 / 8 | |
| 0.6.1 | 11 / 8 | |
| 0.6.0 | 11 / 8 | |
| 0.5.11 | 11 / 8 | |
| 0.5.10 | 11 / 8 | |
| 0.5.9 | 11 / 8 | |
| 0.5.8 | 11 / 8 | |
| 0.5.7 | 11 / 8 | |
| 0.5.6 | 11 / 8 | |
| 0.5.5 | 11 / 8 | |
| 0.5.4 | 11 / 8 | |
| 0.5.3 | 11 / 8 | |
| 0.5.2 | 11 / 8 | |
| 0.5.1 | 11 / 8 | |
| 0.5.0 | 11 / 8 | |
| 0.4.3 | 13 / 8 | |
| 0.4.2 | 13 / 8 | |
| 0.4.1 | 13 / 8 | |
| 0.4.0 | 13 / 8 | |
| 0.3.16 | 13 / 8 | |
| 0.3.15 | 12 / 7 | |
| 0.3.14 | 12 / 7 | |
| 0.3.13 | 12 / 7 | |
| 0.3.12 | 8 / 5 | |
| 0.3.11 | 8 / 5 | |
| 0.3.10 | 8 / 5 | |
| 0.3.9 | 8 / 5 | |
| 0.3.8 | 8 / 5 | |
| 0.3.7 | 8 / 5 | |
| 0.3.6 | 8 / 5 | |
| 0.3.5 | 8 / 5 | |
| 0.3.4 | 8 / 5 | |
| 0.3.3 | 8 / 5 | |
| 0.3.2 | 8 / 5 | |
| 0.3.1 | 8 / 5 | |
| 0.3.0 | 8 / 5 | |
| 0.2.22 | 8 / 5 | |
| 0.2.21 | 8 / 5 | |
| 0.2.20 | 8 / 5 | |
| 0.2.19 | 8 / 5 | |
| 0.2.18 | 8 / 5 | |
| 0.2.17 | 8 / 5 | |
| 0.2.16 | 8 / 5 | |
| 0.2.15 | 8 / 5 | |
| 0.2.14 | 8 / 5 | |
| 0.2.13 | 8 / 5 | |
| 0.2.12 | 8 / 5 | |
| 0.2.11 | 8 / 5 | |
| 0.2.10 | 8 / 5 |
v0.6.4
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
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.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
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.3.5
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.3.4
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.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.