@backstage/backend-dynamic-feature-service
Backstage dynamic feature service
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/backend-plugin-api | AI (dependencies): @backstage/backend-plugin-api is a core package from the same official Backstage monorepo; this dependency relationship is stable and expected across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-auth-node | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-events-node | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-search-common | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-events-backend | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-catalog-backend | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:express-promise-router | AI (phantom-deps): Referenced in config files per the analyzer note; legitimate use in a Backstage backend service package. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-scaffolder-node | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-permission-common | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-search-backend-node | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai | |
| provenance | no-provenance | AI (provenance): Backstage monorepo packages historically published without Sigstore provenance; not a security signal for this established project. | ai | |
| phantom-deps | phantom-dep:@backstage/plugin-permission-node | AI (phantom-deps): Same org scope; used transitively or via plugin API contracts in the Backstage monorepo pattern. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.8.4 | 27 / 8 | |
| 0.8.3 | 27 / 8 | |
| 0.8.2 | 27 / 8 | |
| 0.8.1 | 27 / 8 | |
| 0.8.0 | 27 / 8 | |
| 0.7.9 | 27 / 8 | |
| 0.7.8 | 27 / 8 | |
| 0.7.7 | 27 / 8 | |
| 0.7.6 | 27 / 8 | |
| 0.7.5 | 27 / 8 | |
| 0.7.4 | 27 / 8 | |
| 0.7.3 | 27 / 8 | |
| 0.7.2 | 27 / 8 | |
| 0.7.1 | 27 / 8 | |
| 0.7.0 | 27 / 8 | |
| 0.6.2 | 28 / 7 | |
| 0.6.1 | 25 / 6 | |
| 0.6.0 | 26 / 6 | |
| 0.5.3 | 27 / 5 | |
| 0.5.2 | 27 / 5 | |
| 0.5.1 | 27 / 5 | |
| 0.5.0 | 27 / 5 | |
| 0.4.4 | 27 / 5 | |
| 0.4.3 | 27 / 5 | |
| 0.4.2 | 27 / 5 | |
| 0.4.1 | 27 / 3 | |
| 0.4.0 | 27 / 3 | |
| 0.3.2 | 27 / 3 | |
| 0.3.1 | 27 / 3 | |
| 0.3.0 | 27 / 3 | |
| 0.2.15 | 27 / 3 | |
| 0.2.14 | 27 / 3 | |
| 0.2.13 | 27 / 3 | |
| 0.2.12 | 27 / 3 | |
| 0.2.11 | 27 / 3 | |
| 0.2.10 | 27 / 3 | |
| 0.2.9 | 27 / 3 | |
| 0.2.8 | 27 / 3 | |
| 0.2.7 | 27 / 3 | |
| 0.2.6 | 27 / 3 | |
| 0.2.5 | 27 / 3 | |
| 0.2.4 | 27 / 3 | |
| 0.2.3 | 27 / 3 | |
| 0.2.2 | 27 / 3 | |
| 0.2.1 | 27 / 3 | |
| 0.2.0 | 27 / 3 | |
| 0.1.0 | 22 / 5 |
v0.8.4
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.3
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.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
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.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.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.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.2.10
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.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
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. 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.