@backstage/plugin-devtools-common
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): @backstage/types is a first-party Backstage monorepo package; unvetted status reflects pipeline gap, not actual risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-permission-common | AI (dependencies): @backstage/plugin-permission-common is a first-party Backstage monorepo package; unvetted status reflects pipeline gap, not actual risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Common-library packages in large monorepos typically lack standalone README code blocks and keywords; this is a legitimate internal Backstage plugin package. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 0.1.25 | 2 / 1 | |
| 0.1.24 | 2 / 1 | |
| 0.1.23 | 2 / 1 | |
| 0.1.22 | 2 / 1 | |
| 0.1.21 | 2 / 1 | |
| 0.1.20 | 2 / 1 | |
| 0.1.19 | 2 / 1 | |
| 0.1.18 | 2 / 1 | |
| 0.1.17 | 2 / 1 | |
| 0.1.16 | 2 / 1 | |
| 0.1.15 | 2 / 1 | |
| 0.1.14 | 2 / 1 | |
| 0.1.13 | 2 / 1 | |
| 0.1.12 | 2 / 1 | |
| 0.1.11 | 2 / 1 | |
| 0.1.10 | 2 / 1 | |
| 0.1.9 | 2 / 1 | |
| 0.1.8 | 2 / 1 | |
| 0.1.7 | 2 / 1 | |
| 0.1.6 | 2 / 1 | |
| 0.1.5 | 2 / 1 | |
| 0.1.4 | 2 / 1 | |
| 0.1.3 | 2 / 1 | |
| 0.1.2 | 2 / 1 | |
| 0.1.1 | 2 / 1 | |
| 0.1.0 | 2 / 1 |
v0.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.