@equinor/fusion-framework-react-app
React bindings for building modular Fusion Framework applications. Provides rendering helpers, configuration callbacks, and React hooks for accessing framework modules (HTTP, auth, context, navigation, bookmarks, settings, and more).
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Equinor org package; provenance not used across this package family, stable false positive. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-react | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-module-app | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-module-http | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-app | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-module-navigation | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-react-module-http | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-react-module | AI (dependencies): Same-org monorepo sibling; stable false positive for this package family. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 11.0.0 | 8 / 17 | |
| 10.0.8 | 8 / 16 | |
| 10.0.7 | 8 / 16 | |
| 10.0.6 | 8 / 16 | |
| 10.0.5 | 8 / 16 | |
| 10.0.4 | 8 / 16 | |
| 10.0.2 | 8 / 16 | |
| 10.0.1 | 8 / 16 | |
| 10.0.0 | 8 / 16 | |
| 9.0.8 | 7 / 14 | |
| 9.0.7 | 7 / 14 | |
| 9.0.6 | 7 / 14 | |
| 9.0.5 | 7 / 14 | |
| 9.0.4 | 7 / 14 | |
| 9.0.3 | 7 / 14 | |
| 9.0.2 | 7 / 14 | |
| 9.0.1 | 7 / 14 | |
| 9.0.0 | 7 / 14 | |
| 8.2.0 | 7 / 14 | |
| 8.1.1 | 7 / 14 | |
| 8.0.0 | 7 / 13 |
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.