@backstage/config
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): @backstage/types is a first-party Backstage monorepo package; it is a legitimate dependency for any @backstage/* package and poses no risk. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): @backstage/errors is a first-party Backstage monorepo package; it is a legitimate dependency for any @backstage/* package and poses no risk. | ai | |
| provenance | no-provenance | AI (provenance): Backstage packages historically do not publish Sigstore provenance; the package's legitimacy is well-established through its long history and download volume. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.3.8 | 3 / 2 | |
| 1.3.7 | 3 / 2 | |
| 1.3.6 | 3 / 2 | |
| 1.3.5 | 3 / 2 | |
| 1.3.4 | 3 / 2 | |
| 1.3.3 | 3 / 2 | |
| 1.3.2 | 3 / 2 | |
| 1.3.1 | 3 / 2 | |
| 1.3.0 | 3 / 2 | |
| 1.2.0 | 2 / 2 | |
| 1.1.1 | 3 / 2 | |
| 1.1.0 | 3 / 2 | |
| 1.0.8 | 2 / 3 | |
| 1.0.7 | 2 / 3 | |
| 1.0.6 | 2 / 3 | |
| 1.0.5 | 2 / 3 | |
| 1.0.4 | 2 / 3 | |
| 1.0.3 | 2 / 3 | |
| 1.0.2 | 2 / 3 | |
| 1.0.1 | 2 / 3 | |
| 1.0.0 | 2 / 3 |
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.