@backstage/core-plugin-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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:i18next | AI (phantom-deps): Bundled dist output; new added dep used internally, not scannable via source import. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Framework-scoped types dep, loaded by convention. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Used via TS types/prop validation in build output, not scannable import. | ai | |
| phantom-deps | phantom-dep:zen-observable | AI (phantom-deps): Legit dep used in bundled build, false positive of heuristic. | ai | |
| dependencies | unvetted-dep:zen-observable | AI (dependencies): Well-known observable lib used by Backstage core API, not malicious. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Common in monorepo packages; declared for type usage or indirect imports. No malicious signal. | ai | |
| phantom-deps | phantom-dep:history | AI (phantom-deps): Common in monorepo packages; declared for type usage or indirect imports. No malicious signal. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Same-org sibling package; phantom detection is expected for monorepo type-only dependencies. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages have not historically published with Sigstore provenance; absence is consistent with all prior versions and not a security risk for this well-known package. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org sibling package; phantom detection is expected for monorepo type-only dependencies. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@backstage/version-bridge | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai | |
| dependencies | unvetted-dep:@backstage/frontend-plugin-api | AI (dependencies): First-party @backstage/* sibling package from the same monorepo; not a third-party unknown. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 1.12.8 | 7 / 11 | |
| 1.12.7 | 7 / 11 | |
| 1.12.6 | 7 / 11 | |
| 1.12.5 | 7 / 11 | |
| 1.12.4 | 7 / 11 | |
| 1.12.3 | 7 / 11 | |
| 1.12.2 | 7 / 11 | |
| 1.12.1 | 7 / 11 | |
| 1.12.0 | 6 / 12 | |
| 1.11.1 | 5 / 11 | |
| 1.11.0 | 5 / 11 | |
| 1.10.9 | 5 / 11 | |
| 1.10.8 | 5 / 11 | |
| 1.10.7 | 5 / 11 | |
| 1.10.6 | 5 / 11 | |
| 1.10.5 | 5 / 11 | |
| 1.10.4 | 5 / 11 | |
| 1.10.3 | 5 / 11 | |
| 1.10.2 | 5 / 11 | |
| 1.10.1 | 5 / 11 | |
| 1.10.0 | 5 / 11 | |
| 1.9.4 | 6 / 7 | |
| 1.9.3 | 6 / 7 | |
| 1.9.2 | 6 / 7 | |
| 1.9.1 | 6 / 7 | |
| 1.9.0 | 6 / 7 | |
| 1.8.2 | 5 / 7 | |
| 1.8.1 | 6 / 7 | |
| 1.8.0 | 6 / 7 | |
| 1.7.0 | 6 / 8 | |
| 1.6.0 | 8 / 11 | |
| 1.5.3 | 7 / 12 | |
| 1.5.2 | 7 / 12 | |
| 1.5.1 | 7 / 13 | |
| 1.5.0 | 6 / 12 | |
| 1.4.0 | 6 / 12 | |
| 1.3.0 | 6 / 12 | |
| 1.2.0 | 6 / 12 | |
| 1.1.0 | 6 / 12 | |
| 1.0.7 | 6 / 12 | |
| 1.0.6 | 6 / 12 | |
| 1.0.5 | 7 / 13 | |
| 1.0.4 | 7 / 13 | |
| 1.0.3 | 7 / 13 | |
| 1.0.2 | 7 / 13 | |
| 1.0.1 | 7 / 13 | |
| 1.0.0 | 7 / 13 |
v1.12.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
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.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.9.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.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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.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.6.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.5.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.5.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.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.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.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.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.0.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.0.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.0.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.0.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.0.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.0.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.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.