@backstage/plugin-catalog-backend-module-gerrit
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/config | AI (dependencies): Official @backstage/* monorepo dependency; legitimate and well-established ecosystem package. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official @backstage/* monorepo dependency; legitimate and well-established ecosystem package. | ai | |
| dependencies | unvetted-dep:@backstage/integration | AI (dependencies): Official @backstage/* monorepo dependency; legitimate and well-established ecosystem package. | ai | |
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): Official @backstage/* monorepo dependency; legitimate and well-established ecosystem package. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-node | AI (dependencies): Official @backstage/* monorepo dependency; legitimate and well-established ecosystem package. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-common | AI (dependencies): Official @backstage/* monorepo dependency; legitimate and well-established ecosystem package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-packages commonly lack standalone descriptions/keywords/README code blocks; not indicative of spam or malice. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Common pattern for Backstage monorepo sub-packages; not a malice indicator. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): fs-extra is a legitimate declared dependency; phantom detection may reflect indirect/config usage in monorepo context. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-common | AI (phantom-deps): Same-org monorepo dep; may be used in type-only or indirect positions. Not a risk signal. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is absent but this is common (~88% of npm packages); package age, download count, and repo alignment provide sufficient trust. | ai |
Versions (showing 51 of 59)
| Version | Deps | Published |
|---|---|---|
| 0.3.16 | 8 / 4 | |
| 0.3.15 | 8 / 4 | |
| 0.3.14 | 8 / 4 | |
| 0.3.13 | 9 / 4 | |
| 0.3.12 | 9 / 4 | |
| 0.3.11 | 9 / 4 | |
| 0.3.10 | 9 / 4 | |
| 0.3.9 | 9 / 4 | |
| 0.3.8 | 9 / 4 | |
| 0.3.7 | 9 / 4 | |
| 0.3.6 | 9 / 5 | |
| 0.3.5 | 9 / 5 | |
| 0.3.4 | 9 / 5 | |
| 0.3.3 | 9 / 5 | |
| 0.3.2 | 9 / 5 | |
| 0.3.1 | 9 / 5 | |
| 0.3.0 | 9 / 5 | |
| 0.2.7 | 7 / 5 | |
| 0.2.6 | 7 / 5 | |
| 0.2.5 | 7 / 5 | |
| 0.2.4 | 8 / 5 | |
| 0.2.3 | 8 / 5 | |
| 0.2.2 | 8 / 5 | |
| 0.2.1 | 8 / 5 | |
| 0.2.0 | 8 / 5 | |
| 0.1.39 | 10 / 5 | |
| 0.1.38 | 10 / 5 | |
| 0.1.37 | 10 / 5 | |
| 0.1.36 | 10 / 5 | |
| 0.1.35 | 10 / 5 | |
| 0.1.34 | 10 / 5 | |
| 0.1.33 | 11 / 5 | |
| 0.1.32 | 11 / 5 | |
| 0.1.31 | 11 / 5 | |
| 0.1.30 | 11 / 5 | |
| 0.1.29 | 11 / 5 | |
| 0.1.28 | 11 / 5 | |
| 0.1.27 | 11 / 5 | |
| 0.1.26 | 11 / 5 | |
| 0.1.25 | 11 / 5 | |
| 0.1.24 | 12 / 5 | |
| 0.1.23 | 12 / 5 | |
| 0.1.22 | 12 / 5 | |
| 0.1.21 | 12 / 5 | |
| 0.1.20 | 12 / 5 | |
| 0.1.19 | 12 / 5 | |
| 0.1.18 | 12 / 5 | |
| 0.1.17 | 12 / 5 | |
| 0.1.16 | 12 / 5 | |
| 0.1.15 | 12 / 5 | |
| 0.1.14 | 12 / 5 |
v0.3.16
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.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.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
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.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.