@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, 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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Equinor internal team rotation; publisher has strong track record and no code changes accompany the maintainer update. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with internal team rotation at Equinor; no suspicious code or script changes observed. | ai | |
| 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 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 2.0.14 | 4 / 3 | |
| 2.0.13 | 4 / 3 | |
| 2.0.12 | 4 / 3 | |
| 2.0.11 | 4 / 3 | |
| 2.0.10 | 4 / 3 | |
| 2.0.9 | 4 / 3 | |
| 2.0.8 | 4 / 3 | |
| 2.0.7 | 4 / 3 | |
| 2.0.6 | 4 / 3 | |
| 2.0.5 | 4 / 3 | |
| 2.0.4 | 4 / 3 | |
| 2.0.3 | 4 / 3 | |
| 2.0.1 | 4 / 3 | |
| 2.0.0 | 4 / 3 | |
| 1.1.31 | 4 / 3 | |
| 1.1.30 | 4 / 3 | |
| 1.1.29 | 4 / 3 | |
| 1.1.28 | 4 / 3 | |
| 1.1.27 | 4 / 3 | |
| 1.1.26 | 4 / 3 | |
| 1.1.25 | 4 / 3 | |
| 1.1.24 | 4 / 3 | |
| 1.1.23 | 4 / 3 | |
| 1.1.22 | 4 / 3 | |
| 1.1.21 | 4 / 3 | |
| 1.1.20 | 4 / 3 | |
| 1.1.19 | 4 / 3 | |
| 1.1.18 | 4 / 3 | |
| 1.1.17 | 4 / 3 | |
| 1.1.16 | 4 / 3 | |
| 1.1.15 | 4 / 3 | |
| 1.1.14 | 4 / 3 | |
| 1.1.13 | 4 / 3 | |
| 1.1.12 | 4 / 3 | |
| 1.1.11 | 4 / 3 | |
| 1.1.10 | 4 / 3 |
v2.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.