← Home

@vitessce/glb

npm Repository Homepage
73
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

keller-mark

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from human publisher to GitHub Actions CI/CD is confirmed by SLSA provenance attestation; expected for this monorepo. ai
typosquat typosquat.levenshtein:got AI (typosquat): Same rationale — scoped monorepo package, not a typo of got. ai
phantom-deps phantom-dep:@vitessce/gl AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic unreliable for monorepo builds. ai
phantom-deps phantom-dep:@vitessce/utils AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic unreliable for monorepo builds. ai
phantom-deps phantom-dep:@vitessce/image-utils AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic unreliable for monorepo builds. ai
phantom-deps phantom-dep:@vitessce/spatial-utils AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic unreliable for monorepo builds. ai
typosquat typosquat.levenshtein:glob AI (typosquat): @vitessce/glb is a GLB (3D format) handler in the vitessce monorepo, not a typo of glob. ai
phantom-deps phantom-dep:@vitessce/sets-utils AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic unreliable for monorepo builds. ai
phantom-deps phantom-dep:@vitessce/constants-internal AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic unreliable for monorepo builds. ai
phantom-deps phantom-dep:d3-array AI (phantom-deps): Build-time config reference in monorepo; stable false positive. ai
phantom-deps phantom-dep:lodash-es AI (phantom-deps): Build-time config reference in monorepo; stable false positive. ai
phantom-deps phantom-dep:@react-three/drei AI (phantom-deps): Build-time config reference in monorepo; stable false positive. ai
phantom-deps phantom-dep:@vitessce/error AI (phantom-deps): Sibling monorepo package; phantom-dep heuristic unreliable for monorepo builds. ai

Versions (showing 73 of 73)

Version Deps Published
4.0.1 10 / 6
4.0.0 10 / 6
3.9.11 12 / 5
3.9.10 12 / 5
3.9.9 12 / 5
3.9.8 12 / 5
3.9.7 12 / 5
3.9.6 12 / 5
3.9.5 12 / 5
3.9.4 12 / 5
3.9.3 12 / 5
3.9.2 12 / 5
3.9.1 12 / 5
3.9.0 12 / 5
3.8.13 12 / 5
3.8.10 12 / 5
3.8.9 12 / 5
3.8.8 12 / 5
3.8.7 12 / 5
3.8.6 12 / 5
3.8.5 12 / 5
3.8.4 12 / 5
3.8.3 12 / 5
3.8.2 12 / 5
3.8.1 12 / 5
3.8.0 12 / 5
3.7.1 12 / 0
3.7.0 12 / 0
3.6.18 12 / 0
3.6.17 12 / 0
3.6.16 12 / 0
3.6.15 12 / 0
3.6.14 12 / 0
3.6.13 12 / 0
3.6.12 12 / 0
3.6.11 12 / 0
3.6.10 12 / 0
3.6.9 12 / 0
3.6.8 12 / 0
3.6.7 11 / 0
3.6.6 11 / 0
3.6.5 11 / 0
3.6.4 11 / 0
3.6.3 11 / 0
3.6.2 11 / 0
3.6.1 11 / 0
3.6.0 11 / 0
3.5.12 11 / 0
3.5.11 11 / 0
3.5.10 11 / 0
3.5.9 11 / 0
3.5.8 11 / 0
3.5.7 11 / 0
3.5.6 11 / 0
3.5.5 11 / 0
3.5.4 11 / 0
3.5.3 11 / 0
3.5.2 11 / 0
3.5.1 11 / 0
3.5.0 11 / 0
3.4.14 11 / 0
3.4.12 11 / 0
3.4.11 11 / 0
3.4.10 11 / 0
3.4.9 11 / 0
3.4.8 11 / 0
3.4.7 11 / 0
3.4.6 12 / 1
3.4.5 12 / 1
3.4.4 12 / 1
3.4.3 12 / 1
3.4.2 12 / 1
3.4.1 12 / 1

v4.0.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.0.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v3.5.11

1 finding
LOW No provenance attestation provenance

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

v3.5.10

1 finding
LOW No provenance attestation provenance

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

v3.5.9

1 finding
LOW No provenance attestation provenance

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

v3.5.8

1 finding
LOW No provenance attestation provenance

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

v3.5.7

1 finding
LOW No provenance attestation provenance

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

v3.5.6

1 finding
LOW No provenance attestation provenance

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

v3.5.5

1 finding
LOW No provenance attestation provenance

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

v3.5.4

1 finding
LOW No provenance attestation provenance

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

v3.5.3

1 finding
LOW No provenance attestation provenance

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

v3.5.2

1 finding
LOW No provenance attestation provenance

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

v3.5.1

1 finding
LOW No provenance attestation provenance

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

v3.5.0

1 finding
LOW No provenance attestation provenance

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

v3.4.14

1 finding
LOW No provenance attestation provenance

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

v3.4.12

1 finding
LOW No provenance attestation provenance

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

v3.4.11

1 finding
LOW No provenance attestation provenance

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

v3.4.10

1 finding
LOW No provenance attestation provenance

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

v3.4.9

1 finding
LOW No provenance attestation provenance

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

v3.4.8

1 finding
LOW No provenance attestation provenance

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

v3.4.7

1 finding
LOW No provenance attestation provenance

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

v3.4.6

1 finding
LOW No provenance attestation provenance

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

v3.4.5

1 finding
LOW No provenance attestation provenance

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

v3.4.4

1 finding
LOW No provenance attestation provenance

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

v3.4.3

1 finding
LOW No provenance attestation provenance

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

v3.4.2

1 finding
LOW No provenance attestation provenance

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

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