@backstage/frontend-defaults
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 | no-description | AI (npm-metadata): Backstage monorepo packages often have minimal metadata; this is a library component with proper repo documentation. | ai | |
| provenance | no-provenance | AI (provenance): Provenance is not yet standard practice; absence is not a security concern for established ecosystem packages. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-app | AI (dependencies): Official @backstage/* package from the Backstage monorepo; legitimate and well-established dependency. | ai | |
| dependencies | unvetted-dep:@backstage/core-components | AI (dependencies): Official @backstage/* package from the Backstage monorepo; legitimate and well-established dependency. | ai | |
| dependencies | unvetted-dep:@backstage/frontend-app-api | AI (dependencies): Official @backstage/* package from the Backstage monorepo; legitimate and well-established dependency. | ai | |
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Official @backstage/* package from the Backstage monorepo; legitimate and well-established dependency. | ai | |
| dependencies | unvetted-dep:@react-hookz/web | AI (dependencies): @react-hookz/web is a well-known React hooks library; legitimate dependency for a frontend package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo sub-packages commonly lack standalone descriptions/keywords/README code blocks; not indicative of spam or malice for @backstage/* packages. | ai | |
| phantom-deps | phantom-dep:@react-hookz/web | AI (phantom-deps): Declared in dependencies and used in config/tooling context; not a security concern for this package. | ai | |
| dependencies | unvetted-dep:@backstage/frontend-plugin-api | AI (dependencies): Official @backstage/* package from the Backstage monorepo; legitimate and well-established dependency. | ai | |
| dependencies | unvetted-dep:@backstage/errors | AI (dependencies): Official @backstage/* package from the Backstage monorepo; legitimate and well-established dependency. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 0.5.4 | 7 / 12 | |
| 0.5.3 | 7 / 12 | |
| 0.5.2 | 7 / 12 | |
| 0.5.1 | 7 / 12 | |
| 0.5.0 | 7 / 12 | |
| 0.4.0 | 7 / 10 | |
| 0.3.6 | 7 / 9 | |
| 0.3.5 | 7 / 9 | |
| 0.3.4 | 7 / 9 | |
| 0.3.3 | 7 / 9 | |
| 0.3.2 | 7 / 9 | |
| 0.3.1 | 7 / 9 | |
| 0.3.0 | 7 / 9 | |
| 0.2.4 | 6 / 9 | |
| 0.2.3 | 6 / 9 | |
| 0.2.2 | 6 / 9 | |
| 0.2.1 | 6 / 9 | |
| 0.2.0 | 6 / 9 | |
| 0.1.6 | 6 / 9 | |
| 0.1.5 | 6 / 9 | |
| 0.1.4 | 6 / 9 | |
| 0.1.3 | 6 / 9 | |
| 0.1.2 | 6 / 9 | |
| 0.1.1 | 6 / 9 | |
| 0.1.0 | 7 / 5 |
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
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.6
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.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.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.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
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. 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.