@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, 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:@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 34 of 34)
| Version | Deps | Published |
|---|---|---|
| 4.0.13 | 5 / 6 | |
| 4.0.12 | 5 / 6 | |
| 4.0.11 | 5 / 6 | |
| 4.0.10 | 5 / 6 | |
| 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 | |
| 4.0.0 | 5 / 6 | |
| 3.1.11 | 5 / 6 | |
| 3.1.10 | 5 / 6 | |
| 3.1.9 | 5 / 6 | |
| 3.1.8 | 5 / 6 | |
| 3.1.7 | 5 / 6 | |
| 3.1.6 | 5 / 6 | |
| 3.1.5 | 5 / 6 | |
| 3.1.4 | 5 / 6 | |
| 3.1.3 | 5 / 6 | |
| 3.1.2 | 5 / 6 | |
| 3.1.1 | 5 / 6 | |
| 3.1.0 | 6 / 7 | |
| 3.0.7 | 6 / 7 | |
| 3.0.6 | 6 / 7 | |
| 3.0.5 | 6 / 7 | |
| 3.0.4 | 6 / 7 | |
| 3.0.3 | 6 / 7 | |
| 3.0.2 | 6 / 7 | |
| 3.0.1 | 6 / 7 | |
| 3.0.0 | 1 / 12 | |
| 2.0.2 | 1 / 12 |
v4.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.