@backstage/backend-openapi-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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established Backstage monorepo package with 1114 days history and 142k weekly downloads; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): Type-only dependency for TypeScript; framework-scoped, loaded by convention in Backstage packages. | ai | |
| phantom-deps | phantom-dep:@types/express-serve-static-core | AI (phantom-deps): Type-only dependency for TypeScript; framework-scoped, loaded by convention in Backstage packages. | ai | |
| phantom-deps | phantom-dep:@backstage/types | AI (phantom-deps): Same-org Backstage package; may be used transitively or via type imports. Not a security concern. | ai | |
| phantom-deps | phantom-dep:@backstage/backend-plugin-api | AI (phantom-deps): Same-org Backstage package; may be used transitively or via type imports. Not a security concern. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash is declared as a dependency; phantom detection may be a false positive due to indirect usage patterns in the Backstage build system. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.6.9 | 16 / 4 | |
| 0.6.8 | 16 / 4 | |
| 0.6.7 | 16 / 4 | |
| 0.6.6 | 16 / 4 | |
| 0.6.5 | 16 / 4 | |
| 0.6.4 | 16 / 4 | |
| 0.6.3 | 16 / 4 | |
| 0.6.2 | 16 / 4 | |
| 0.6.1 | 16 / 4 | |
| 0.6.0 | 16 / 4 | |
| 0.5.5 | 16 / 4 | |
| 0.5.4 | 16 / 4 | |
| 0.5.3 | 16 / 4 |
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.