@backstage/frontend-dynamic-feature-loader
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@backstage/config | AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for all @backstage/* packages. | ai | |
| dependencies | unvetted-dep:@backstage/frontend-plugin-api | AI (dependencies): Core Backstage monorepo dependency; legitimate and expected for @backstage frontend packages. | ai | |
| dependencies | unvetted-dep:@backstage/module-federation-common | AI (dependencies): Backstage-scoped module federation utility; legitimate sibling package in the Backstage monorepo. | ai | |
| dependencies | unvetted-dep:uri-template | AI (dependencies): Well-known URI template library; no malicious indicators. Legitimate runtime dependency. | ai | |
| phantom-deps | phantom-dep:@backstage/config | AI (phantom-deps): Used via configSchema/config.d.ts pattern standard in Backstage packages; not a direct import but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@module-federation/sdk | AI (phantom-deps): Referenced in config/build files as noted by analyzer; legitimate for module federation packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.1.12 | 8 / 9 | |
| 0.1.11 | 8 / 9 | |
| 0.1.10 | 8 / 9 | |
| 0.1.9 | 8 / 9 | |
| 0.1.8 | 7 / 9 | |
| 0.1.7 | 7 / 9 | |
| 0.1.6 | 7 / 9 | |
| 0.1.5 | 7 / 9 | |
| 0.1.4 | 7 / 9 | |
| 0.1.3 | 7 / 9 | |
| 0.1.2 | 7 / 9 | |
| 0.1.1 | 7 / 9 |
v0.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.