← Home

@webviz/subsurface-viewer

npm Homepage

3D visualization component for subsurface reservoir data

8
Versions
MPL-2.0
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

akia

Keywords

subsurfacereactwellswelllogsgridsfaultsreservoir

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Equinor org package with long publish history; provenance not yet enabled but no other risk signals. ai
phantom-deps phantom-dep:d3 AI (phantom-deps): d3 is declared and used transitively/via config; stable FP for this package. ai
phantom-deps phantom-dep:ajv AI (phantom-deps): ajv declared and used via config/schema validation; stable FP. ai
phantom-deps phantom-dep:d3-format AI (phantom-deps): d3-format declared and used transitively/via config; stable FP. ai
phantom-deps phantom-dep:@turf/simplify AI (phantom-deps): @turf/simplify declared and used via config; stable FP. ai

Versions (showing 8 of 8)

Version Deps Published
1.18.1 18 / 3
1.17.8 27 / 3
1.17.7 27 / 3
1.17.6 27 / 3
1.17.5 27 / 3
1.17.4 27 / 3
1.17.3 27 / 3
1.17.2 27 / 3

v1.18.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.17.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.17.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.