@backstage/plugin-catalog-backend-module-puppetdb
A Backstage catalog backend module that helps integrate towards PuppetDB
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
Keywords
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): Core @backstage/* package from the official Backstage monorepo; stable ecosystem dependency, not a security risk. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Core @backstage/* package from the official Backstage monorepo; stable ecosystem dependency, not a security risk. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Core @backstage/* package from the official Backstage monorepo; stable ecosystem dependency, not a security risk. | ai | |
| dependencies | unvetted-dep:@backstage/catalog-model | AI (dependencies): Core @backstage/* package from the official Backstage monorepo; stable ecosystem dependency, not a security risk. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Core @backstage/* package from the official Backstage monorepo; stable ecosystem dependency, not a security risk. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): Core @backstage/* package from the official Backstage monorepo; stable ecosystem dependency, not a security risk. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages are not published with Sigstore provenance; this is consistent across all versions and not a security concern. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.2.24 | 7 / 4 | |
| 0.2.23 | 7 / 4 | |
| 0.2.22 | 7 / 4 | |
| 0.2.21 | 8 / 4 | |
| 0.2.20 | 8 / 4 | |
| 0.2.19 | 8 / 4 | |
| 0.2.18 | 8 / 4 | |
| 0.2.17 | 8 / 4 | |
| 0.2.16 | 8 / 4 | |
| 0.2.15 | 8 / 4 | |
| 0.2.14 | 9 / 4 | |
| 0.2.13 | 9 / 4 | |
| 0.2.12 | 9 / 4 | |
| 0.2.11 | 9 / 4 | |
| 0.2.10 | 9 / 4 | |
| 0.2.9 | 9 / 4 | |
| 0.2.8 | 9 / 4 | |
| 0.2.7 | 9 / 4 | |
| 0.2.6 | 9 / 4 | |
| 0.2.5 | 9 / 4 | |
| 0.2.4 | 10 / 4 | |
| 0.2.3 | 10 / 4 | |
| 0.2.2 | 10 / 4 | |
| 0.2.1 | 10 / 4 | |
| 0.2.0 | 10 / 4 | |
| 0.1.28 | 12 / 4 | |
| 0.1.27 | 12 / 4 | |
| 0.1.26 | 12 / 4 | |
| 0.1.25 | 12 / 4 | |
| 0.1.24 | 12 / 4 |
v0.2.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
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.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
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.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.