@equinor/fusion-framework-module-service-discovery
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 monorepo package; provenance not yet configured but publisher track record is clean. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-query | AI (dependencies): Same Equinor monorepo family; stable sibling dependency pattern across all versions. | ai | |
| dependencies | unvetted-dep:@equinor/fusion-framework-module-http | AI (dependencies): Same Equinor monorepo family; stable sibling dependency pattern across all versions. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 10.0.1 | 5 / 1 | |
| 10.0.0 | 5 / 1 | |
| 9.1.1 | 5 / 1 | |
| 9.1.0 | 5 / 1 | |
| 9.0.5 | 5 / 1 |
v10.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.1.0
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.