@backstage/config-loader
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:yup | AI (phantom-deps): Schema validation lib likely used in bundled dist output, not a supply-chain concern. | ai | |
| phantom-deps | phantom-dep:@backstage/cli-common | AI (phantom-deps): Same-org scoped dep, likely used by convention/build tooling. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): First-party @backstage/* package from the official Backstage monorepo; unvetted status is a registry artifact, not a risk. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): First-party @backstage/* package from the official Backstage monorepo; unvetted status is a registry artifact, not a risk. | ai | |
| phantom-deps | phantom-dep:@types/json-schema | AI (phantom-deps): @types/json-schema is intentionally used at runtime in Backstage config-loader for JSON schema validation; this is a stable, documented pattern for this package. | ai | |
| dependencies | unvetted-dep:@backstage/cli-common | AI (dependencies): First-party @backstage/* package from the official Backstage monorepo; unvetted status is a registry artifact, not a risk. | ai | |
| dependencies | unvetted-dep:typescript-json-schema | AI (dependencies): Well-known, widely-used TypeScript-to-JSON-schema library; legitimate dependency for a config-loader package. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): First-party @backstage/* package from the official Backstage monorepo; unvetted status is a registry artifact, not a risk. | ai | |
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package with 2147 days of history; lack of Sigstore provenance is not a risk signal for this well-known package. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.11.0 | 15 / 6 | |
| 1.10.12 | 14 / 6 | |
| 1.10.11 | 15 / 6 | |
| 1.10.10 | 15 / 6 | |
| 1.10.9 | 15 / 6 | |
| 1.10.8 | 15 / 6 | |
| 1.10.7 | 15 / 6 | |
| 1.10.6 | 15 / 6 | |
| 1.10.5 | 15 / 6 | |
| 1.10.4 | 15 / 6 | |
| 1.10.3 | 15 / 6 | |
| 1.10.2 | 15 / 6 | |
| 1.10.1 | 15 / 6 | |
| 1.10.0 | 15 / 6 | |
| 1.9.6 | 15 / 5 | |
| 1.9.5 | 15 / 5 | |
| 1.9.4 | 15 / 5 | |
| 1.9.3 | 15 / 5 | |
| 1.9.2 | 16 / 5 | |
| 1.9.1 | 16 / 5 | |
| 1.9.0 | 16 / 5 | |
| 1.8.1 | 16 / 5 | |
| 1.8.0 | 16 / 5 | |
| 1.7.0 | 16 / 5 | |
| 1.6.2 | 16 / 5 | |
| 1.6.1 | 16 / 5 | |
| 1.6.0 | 16 / 6 | |
| 1.5.3 | 16 / 6 | |
| 1.5.2 | 16 / 6 | |
| 1.5.1 | 16 / 6 | |
| 1.5.0 | 17 / 8 | |
| 1.4.0 | 17 / 9 | |
| 1.3.2 | 17 / 9 | |
| 1.3.1 | 17 / 9 | |
| 1.3.0 | 17 / 9 | |
| 1.2.0 | 15 / 7 | |
| 1.1.9 | 15 / 7 | |
| 1.1.8 | 15 / 7 | |
| 1.1.7 | 15 / 7 | |
| 1.1.6 | 15 / 7 | |
| 1.1.5 | 15 / 7 | |
| 1.1.4 | 15 / 7 | |
| 1.1.3 | 15 / 7 | |
| 1.1.2 | 15 / 7 | |
| 1.1.1 | 15 / 7 | |
| 1.1.0 | 15 / 7 | |
| 1.0.0 | 15 / 7 |
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
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.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
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.5.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.4.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.3.2
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.3.1
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
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.1.8
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.1.7
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.1.6
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.1.5
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.1.4
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.1.3
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.1.2
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.1.1
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.1.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.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.