@backstage/core-compat-api
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Backstage monorepo uses 0.0.0 placeholder versioning convention across its packages. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework type-only dep loaded by convention. | ai | |
| phantom-deps | phantom-dep:@backstage/core-app-api | AI (phantom-deps): Same-org Backstage dependency, not a real risk. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package with clear role metadata and repository context; missing description is benign for this package type. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is not yet standard practice; absence is not a security signal for established packages with strong ecosystem trust. | ai | |
| dependencies | unvetted-dep:@backstage/filter-predicates | AI (dependencies): Same-org @backstage/* dependency from the official Backstage monorepo; expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@backstage/frontend-plugin-api | AI (dependencies): Same-org @backstage/* dependency from the official Backstage monorepo; expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-catalog-react | AI (dependencies): Same-org @backstage/* dependency from the official Backstage monorepo; expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): Same-org @backstage/* dependency from the official Backstage monorepo; expected and legitimate for this package. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org @backstage/* package; phantom detection is expected for type-only or indirect usage in the Backstage monorepo ecosystem. | ai | |
| phantom-deps | phantom-dep:@backstage/filter-predicates | AI (phantom-deps): Same-org @backstage/* package; phantom detection is expected for indirect usage patterns in the Backstage monorepo ecosystem. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is listed as a runtime dependency with a broad version range (v3/v4); phantom detection likely reflects conditional/indirect usage patterns in this Backstage package. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Same-org @backstage/* dependency from the official Backstage monorepo; expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@backstage/version-bridge | AI (dependencies): Same-org @backstage/* dependency from the official Backstage monorepo; expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@backstage/core-plugin-api | AI (dependencies): Same-org @backstage/* dependency from the official Backstage monorepo; expected and legitimate for this package. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-app-react | AI (dependencies): Same-org @backstage/* dependency from the official Backstage monorepo; expected and legitimate for this package. | ai |
Versions (showing 38 of 38)
| Version | Deps | Published |
|---|---|---|
| 0.5.13 | 9 / 12 | |
| 0.5.12 | 9 / 12 | |
| 0.5.11 | 9 / 12 | |
| 0.5.10 | 10 / 14 | |
| 0.5.9 | 10 / 14 | |
| 0.5.8 | 8 / 14 | |
| 0.5.7 | 7 / 14 | |
| 0.5.6 | 7 / 14 | |
| 0.5.5 | 7 / 14 | |
| 0.5.4 | 7 / 14 | |
| 0.5.3 | 5 / 14 | |
| 0.5.2 | 5 / 14 | |
| 0.5.1 | 5 / 14 | |
| 0.5.0 | 5 / 14 | |
| 0.4.4 | 5 / 14 | |
| 0.4.3 | 5 / 17 | |
| 0.4.2 | 5 / 17 | |
| 0.4.1 | 5 / 17 | |
| 0.4.0 | 5 / 17 | |
| 0.3.6 | 4 / 17 | |
| 0.3.5 | 4 / 17 | |
| 0.3.4 | 4 / 17 | |
| 0.3.3 | 4 / 17 | |
| 0.3.2 | 4 / 17 | |
| 0.3.1 | 4 / 17 | |
| 0.3.0 | 5 / 11 | |
| 0.2.8 | 5 / 11 | |
| 0.2.7 | 4 / 10 | |
| 0.2.6 | 4 / 10 | |
| 0.2.5 | 4 / 10 | |
| 0.2.4 | 4 / 10 | |
| 0.2.3 | 5 / 9 | |
| 0.2.2 | 5 / 9 | |
| 0.2.1 | 5 / 9 | |
| 0.2.0 | 5 / 9 | |
| 0.1.1 | 5 / 9 | |
| 0.1.0 | 5 / 8 | |
| 0.0.0 | 4 / 5 |
v0.5.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.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.
v0.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.
v0.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.