@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, 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:express-promise-router | AI (phantom-deps): Likely used via re-export/bundling in this OpenAPI utils lib; no malicious indicator. | 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 | |
| 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:@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 | |
| 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 |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.7.0 | 16 / 4 | |
| 0.6.10 | 16 / 4 | |
| 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 | |
| 0.5.2 | 16 / 4 | |
| 0.5.1 | 16 / 4 | |
| 0.5.0 | 16 / 4 | |
| 0.4.1 | 16 / 4 | |
| 0.4.0 | 16 / 4 | |
| 0.3.0 | 16 / 4 | |
| 0.2.0 | 17 / 3 | |
| 0.1.18 | 11 / 2 | |
| 0.1.17 | 11 / 2 | |
| 0.1.16 | 11 / 2 | |
| 0.1.15 | 11 / 2 | |
| 0.1.14 | 11 / 2 | |
| 0.1.13 | 11 / 2 | |
| 0.1.12 | 11 / 2 | |
| 0.1.11 | 11 / 2 | |
| 0.1.10 | 11 / 2 | |
| 0.1.9 | 11 / 2 | |
| 0.1.8 | 11 / 2 | |
| 0.1.7 | 11 / 2 | |
| 0.1.6 | 11 / 2 | |
| 0.1.5 | 11 / 2 | |
| 0.1.4 | 11 / 2 | |
| 0.1.3 | 11 / 2 | |
| 0.1.2 | 11 / 2 | |
| 0.1.1 | 12 / 2 | |
| 0.1.0 | 12 / 2 | |
| 0.0.5 | 9 / 2 | |
| 0.0.4 | 9 / 2 | |
| 0.0.3 | 9 / 2 | |
| 0.0.2 | 6 / 1 | |
| 0.0.1 | 6 / 1 |
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
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.1
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.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.13
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.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.
v0.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.
v0.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.
v0.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.