@backstage/frontend-test-utils
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are first-party @backstage packages and zod, a standard schema lib. | ai | |
| dependencies | unvetted-dep:zen-observable | AI (dependencies): zen-observable is a well-known observable library used broadly in the JS ecosystem; its use in Backstage test utils is legitimate and expected. | ai | |
| dependencies | unvetted-dep:@backstage/plugin-app | AI (dependencies): @backstage/plugin-app is a first-party Backstage package in the same org scope; its use in frontend-test-utils is expected and legitimate across all versions. | ai | |
| phantom-deps | phantom-dep:@backstage/version-bridge | AI (phantom-deps): Same org scope (@backstage); phantom dep pattern is common in Backstage monorepo packages where deps are used for type resolution or transitive purposes. | ai | |
| provenance | no-provenance | AI (provenance): Backstage uses automated CI publishing; lack of Sigstore provenance is consistent across the ecosystem and not a risk indicator here. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): zod is listed as a runtime dependency in package.json; phantom-dep flag likely due to indirect usage or type-only imports in this test utility package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo package from the official Backstage project; missing description is a known pattern for internal packages in large monorepos. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.6.0 | 16 / 9 | |
| 0.5.2 | 16 / 9 | |
| 0.5.1 | 16 / 9 | |
| 0.5.0 | 15 / 9 | |
| 0.4.5 | 9 / 6 | |
| 0.4.4 | 9 / 6 | |
| 0.4.3 | 8 / 6 | |
| 0.4.2 | 8 / 6 | |
| 0.4.1 | 8 / 6 | |
| 0.4.0 | 8 / 6 | |
| 0.3.6 | 8 / 6 | |
| 0.3.5 | 8 / 6 | |
| 0.3.4 | 8 / 6 | |
| 0.3.3 | 8 / 6 | |
| 0.3.2 | 8 / 6 | |
| 0.3.1 | 8 / 6 | |
| 0.3.0 | 8 / 6 | |
| 0.2.6 | 8 / 6 | |
| 0.2.5 | 8 / 6 | |
| 0.2.4 | 8 / 6 | |
| 0.2.3 | 8 / 6 | |
| 0.2.2 | 8 / 6 | |
| 0.2.1 | 8 / 6 | |
| 0.2.0 | 8 / 3 | |
| 0.1.12 | 5 / 3 | |
| 0.1.11 | 4 / 3 | |
| 0.1.10 | 4 / 3 | |
| 0.1.9 | 4 / 3 | |
| 0.1.8 | 4 / 3 | |
| 0.1.7 | 4 / 3 | |
| 0.1.6 | 4 / 3 | |
| 0.1.5 | 4 / 3 | |
| 0.1.4 | 4 / 3 | |
| 0.1.3 | 4 / 3 | |
| 0.1.2 | 4 / 3 | |
| 0.1.1 | 4 / 3 | |
| 0.1.0 | 4 / 3 |
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.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. 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.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.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.8
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.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.
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. 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.