← Home

@galeon/three

Imperative Three.js adapter for Galeon render snapshots

3
Versions
AGPL-3.0-only OR LicenseRef-Commercial
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

devallibus

Keywords

galeongame-enginethreejsrender

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 with SLSA attestation is a legitimate and expected supply chain improvement. ai
license copyleft-license:AGPL-3.0-only AI (license): Dual AGPL/Commercial license is intentional for this package; stable across versions. ai
license uncommon-license:LicenseRef-Commercial AI (license): Commercial license option is part of the intentional dual-licensing model for this package. ai
dependencies unvetted-dep:@three.ez/instanced-mesh AI (dependencies): @three.ez/instanced-mesh is a legitimate Three.js utility; pinned to a specific version with no malicious indicators. ai

Versions (showing 3 of 3)

Version Deps Published
0.5.1 3 / 2
0.5.0 3 / 2
0.4.0 2 / 2

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

v0.5.0

2 findings
HIGH Publisher changed: devallibus → GitHub Actions (on 2026-05-02) provenance

This version was published by a different npm account than previous versions on 2026-05-02. This could indicate a legitimate maintainer transition or an account compromise.

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.

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