@backstage/catalog-model
Types and validators that help describe the model of a Backstage Catalog
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:uuid | AI (phantom-deps): Legitimate Backstage library dep, likely used via compiled output. | ai | |
| phantom-deps | phantom-dep:json-schema | AI (phantom-deps): Legitimate validation dep used in schema definitions. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org first-party dep, standard monorepo pattern. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): @backstage/types is a first-party Backstage monorepo package; unvetted status is a registry bootstrapping artifact, not a real risk. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): @backstage/errors is a first-party Backstage monorepo package; unvetted status is a registry bootstrapping artifact, not a real risk. | ai | |
| provenance | no-provenance | AI (provenance): Backstage does not publish with Sigstore provenance; consistent across all their packages and not a meaningful risk signal for this well-established project. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.9.0 | 6 / 4 | |
| 1.8.0 | 6 / 4 | |
| 1.7.7 | 4 / 4 | |
| 1.7.6 | 4 / 4 | |
| 1.7.5 | 4 / 4 | |
| 1.7.4 | 4 / 4 | |
| 1.7.3 | 4 / 4 | |
| 1.7.2 | 4 / 4 | |
| 1.7.1 | 4 / 4 | |
| 1.7.0 | 4 / 4 | |
| 1.6.0 | 4 / 4 | |
| 1.5.0 | 4 / 4 | |
| 1.4.5 | 4 / 4 | |
| 1.4.4 | 4 / 4 | |
| 1.4.3 | 4 / 4 | |
| 1.4.2 | 7 / 4 | |
| 1.4.1 | 7 / 4 | |
| 1.4.0 | 7 / 4 | |
| 1.3.0 | 7 / 4 | |
| 1.2.1 | 7 / 4 | |
| 1.2.0 | 7 / 4 |
v1.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
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.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.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.4.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.4.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.4.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.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.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.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.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.