@backstage/frontend-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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): Type-only dep used by convention, not direct import. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Backstage monorepo convention across many packages; not indicative of malware here. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash is properly declared in dependencies and referenced in config; phantom-dep rule is a false positive for library packages. | ai | |
| phantom-deps | phantom-dep:@backstage/core-components | AI (phantom-deps): @backstage/core-components is properly declared in dependencies; same-org scope is expected in monorepo packages. | ai | |
| phantom-deps | phantom-dep:@material-ui/core | AI (phantom-deps): @material-ui/core is properly declared in dependencies and referenced in config; phantom-dep rule is a false positive for library packages. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is not yet standard; absence is not a risk signal for established ecosystem packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo library package; missing description is common and not a malware signal in this context. | ai | |
| dependencies | unvetted-dep:@backstage/types | AI (dependencies): First-party Backstage monorepo package; legitimate sibling dependency with no malicious indicators. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo package; missing description/keywords/README code blocks are typical for internal packages in large OSS monorepos like Backstage. | ai | |
| dependencies | unvetted-dep:@backstage/filter-predicates | AI (dependencies): First-party Backstage monorepo package; legitimate sibling dependency with no malicious indicators. | ai | |
| dependencies | unvetted-dep:@backstage/version-bridge | AI (dependencies): First-party Backstage monorepo package; legitimate sibling dependency with no malicious indicators. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): First-party Backstage monorepo package; legitimate sibling dependency with no malicious indicators. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.17.3 | 8 / 11 | |
| 0.17.2 | 8 / 11 | |
| 0.17.1 | 8 / 11 | |
| 0.17.0 | 7 / 12 | |
| 0.16.2 | 7 / 12 | |
| 0.16.1 | 7 / 12 | |
| 0.16.0 | 7 / 12 | |
| 0.15.1 | 6 / 12 | |
| 0.15.0 | 6 / 12 | |
| 0.14.1 | 5 / 12 | |
| 0.14.0 | 5 / 12 | |
| 0.13.4 | 5 / 12 | |
| 0.13.3 | 5 / 12 | |
| 0.13.2 | 5 / 12 | |
| 0.13.1 | 8 / 11 | |
| 0.13.0 | 8 / 11 | |
| 0.12.1 | 8 / 11 | |
| 0.12.0 | 8 / 11 | |
| 0.11.0 | 8 / 11 | |
| 0.10.4 | 8 / 11 | |
| 0.10.3 | 8 / 11 | |
| 0.10.2 | 8 / 11 | |
| 0.10.1 | 8 / 11 | |
| 0.10.0 | 8 / 11 | |
| 0.9.5 | 8 / 11 | |
| 0.9.4 | 8 / 11 | |
| 0.9.3 | 8 / 11 | |
| 0.9.2 | 8 / 11 | |
| 0.9.1 | 8 / 11 | |
| 0.9.0 | 8 / 11 | |
| 0.8.0 | 9 / 7 | |
| 0.7.0 | 9 / 7 | |
| 0.6.7 | 9 / 7 | |
| 0.6.6 | 9 / 7 | |
| 0.6.5 | 9 / 7 | |
| 0.6.4 | 9 / 7 | |
| 0.6.3 | 9 / 7 | |
| 0.6.2 | 9 / 7 | |
| 0.6.1 | 9 / 7 | |
| 0.6.0 | 9 / 7 | |
| 0.5.0 | 9 / 7 | |
| 0.4.0 | 10 / 7 | |
| 0.3.0 | 9 / 6 | |
| 0.2.0 | 6 / 5 | |
| 0.1.0 | 6 / 5 | |
| 0.0.0 | 6 / 4 |
v0.17.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.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.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
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.0
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.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.