@equinor/fusion-framework-dev-server
Package for running a development server for fusion-framework
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established @equinor org publisher with 144 approved packages; dormancy reflects org release cadence, not takeover risk. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-log | AI (dependencies): Internal Equinor fusion-framework ecosystem dependency; expected and stable for this package. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-vite-plugin-api-service | AI (dependencies): Internal Equinor fusion-framework ecosystem dependency; expected and stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Equinor monorepo package; lack of provenance is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 2.0.7 | 4 / 3 | |
| 2.0.5 | 4 / 3 | |
| 2.0.4 | 4 / 3 | |
| 2.0.3 | 4 / 3 | |
| 2.0.1 | 4 / 3 |
v2.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.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.
v2.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.