@shapediver/viewer.rendering-engine.intersection-restriction-engine polyform-noncommercial-1.0.0 42 versions

@shapediver/viewer.rendering-engine.intersection-restriction-engine

npm Repository Homepage

This package is part of the [`@shapediver/viewer`](https://www.npmjs.com/package/@shapediver/viewer), you can find all information [here](https://viewer.shapediver.com/v3/latest/api/index.html).

42

Versions

polyform-noncommercial-1.0.0

License

No

Install Scripts

Attested

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

snabelamichael_at_shapedivermatt_at_shapediverdmitry_at_shapediver

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@shapediver/viewer.rendering-engine.rendering-engine-threejs	AI (dependencies): Same-org monorepo sibling dependency; consistent pattern across all ShapeDiver viewer packages.	ai	2026/04/30
bogus-package	bogus-package	AI (bogus-package): Internal monorepo sub-package; sparse README and no keywords are expected for org-internal modules.	ai	2026/04/29
phantom-deps	phantom-dep:@types/three	AI (phantom-deps): Type-only dev dependency; not imported at runtime, stable false positive for this package.	ai	2026/04/29
phantom-deps	phantom-dep:@shapediver/viewer.rendering-engine.intersection-engine	AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo internal packages.	ai	2026/04/29

Versions (showing 42 of 143)

Version	Deps	Published
3.9.10	10 / 0	2025-05-08
3.9.9	10 / 0	2025-04-30
3.9.8	10 / 0	2025-04-25
3.9.7	10 / 0	2025-04-23
3.9.6	10 / 0	2025-04-04
3.9.5	10 / 0	2025-04-01
3.9.4	10 / 0	2025-03-26
3.9.3	10 / 0	2025-03-26
3.9.2	10 / 0	2025-03-26
3.9.1	10 / 0	2025-03-25
3.9.0	10 / 0	2025-03-20
3.8.15	10 / 0	2025-03-13
3.8.14	10 / 0	2025-03-13
3.8.13	10 / 0	2025-03-11
3.8.12	10 / 0	2025-03-04
3.8.11	10 / 0	2025-03-04
3.8.10	10 / 0	2025-02-28
3.8.9	10 / 0	2025-02-28
3.8.8	10 / 0	2025-02-26
3.8.7	10 / 0	2025-02-26
3.8.6	10 / 0	2025-02-25
3.8.5	10 / 0	2025-02-24
3.8.4	10 / 0	2025-02-20
3.8.3	10 / 0	2025-02-19
3.8.2	10 / 0	2025-02-18
3.8.1	10 / 0	2025-02-18
3.8.0	10 / 0	2025-02-17
3.7.5	10 / 0	2025-02-14
3.7.4	10 / 0	2025-02-06
3.7.3	10 / 0	2025-01-22
3.7.2	10 / 0	2025-01-09
3.7.1	10 / 0	2025-01-08
3.7.0	10 / 0	2024-12-09
3.6.0	10 / 0	2024-11-21
3.5.7	10 / 0	2024-11-20
3.5.6	10 / 0	2024-11-20
3.5.5	10 / 0	2024-11-19
3.5.4	10 / 0	2024-11-18
3.5.3	10 / 0	2024-11-18
3.5.2	10 / 0	2024-11-15
3.5.1	10 / 0	2024-11-14
3.5.0	10 / 0	2024-11-12

v3.9.8

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.

v3.9.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.

v3.9.6

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.

v3.9.5

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.

v3.9.4

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.

v3.9.3

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.

v3.9.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.

v3.9.1

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.

v3.9.0

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.

v3.8.15

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.

v3.8.14

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.

v3.8.13

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.

v3.8.12

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.

v3.8.11

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.

v3.8.10

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.

v3.8.9

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.

v3.8.8

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.

v3.8.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.

v3.8.6

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.

v3.8.5

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.

v3.8.4

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.

v3.8.3

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.

v3.8.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.

v3.8.1

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.

v3.8.0

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.

v3.7.5

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.

v3.7.4

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.

v3.7.3

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.

v3.7.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.

v3.7.1

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.

v3.7.0

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.

v3.6.0

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.

v3.5.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.

v3.5.6

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.

v3.5.5

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.

v3.5.4

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.

v3.5.3

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.

v3.5.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.

v3.5.1

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.

v3.5.0

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.