@equinor/fusion-framework-vite-plugin-spa
Vite plugin for SPA development
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@equinor/fusion-framework-module-http | AI (dependencies): First-party Equinor fusion-framework sibling package from same monorepo. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-module-msal | AI (dependencies): First-party Equinor fusion-framework sibling package from same monorepo. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-module-telemetry | AI (dependencies): First-party Equinor fusion-framework sibling package from same monorepo. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-module-service-discovery | AI (dependencies): First-party Equinor fusion-framework sibling package from same monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Established Equinor monorepo package; lack of provenance is consistent across all versions of this org's packages. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.0.9 | 5 / 6 | |
| 4.0.8 | 5 / 6 | |
| 4.0.7 | 5 / 6 | |
| 4.0.6 | 5 / 6 | |
| 4.0.5 | 5 / 6 | |
| 4.0.4 | 5 / 6 | |
| 4.0.3 | 5 / 6 | |
| 4.0.1 | 5 / 6 |
v4.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.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.
v4.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.