@backstage/plugin-events-backend-test-utils
The plugin-events-backend-test-utils for @backstage/plugin-events-node
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
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 utility/test package; short README and no keywords are expected for internal packages in large monorepos, not spam indicators. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package with 1000+ versions; lack of Sigstore provenance is a known gap for this package family, not a risk signal. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.1.55 | 1 / 1 | |
| 0.1.54 | 1 / 1 | |
| 0.1.53 | 1 / 1 | |
| 0.1.52 | 1 / 1 | |
| 0.1.51 | 1 / 1 | |
| 0.1.50 | 1 / 1 | |
| 0.1.49 | 1 / 1 | |
| 0.1.48 | 1 / 1 | |
| 0.1.47 | 1 / 1 | |
| 0.1.46 | 1 / 1 | |
| 0.1.45 | 1 / 1 | |
| 0.1.44 | 1 / 1 |
v0.1.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.49
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
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.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.