@galacean/effects-threejs
Galacean Effects runtime threejs plugin for the web
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| email-domain | unclaimed-email:yufangjun.com | AI (email-domain): Long-lived Ant Group package; domain risk is theoretical with no evidence of active hijack across 252 versions. | ai | |
| provenance | no-provenance | AI (provenance): Large org package with 250 versions; lack of provenance is consistent across all releases. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 2.9.3 | 1 / 2 | |
| 2.9.2 | 1 / 2 | |
| 2.9.1 | 1 / 2 | |
| 2.9.0 | 1 / 2 | |
| 2.8.12 | 1 / 2 | |
| 2.8.11 | 1 / 2 | |
| 2.8.10 | 1 / 2 | |
| 2.8.9 | 1 / 2 | |
| 2.8.8 | 1 / 2 | |
| 2.8.7 | 1 / 2 | |
| 2.8.6 | 1 / 2 | |
| 2.8.5 | 1 / 2 | |
| 2.8.4 | 1 / 2 | |
| 2.8.3 | 1 / 2 | |
| 2.8.2 | 1 / 2 | |
| 2.8.1 | 1 / 2 | |
| 2.8.0 | 1 / 2 | |
| 2.7.5 | 1 / 2 | |
| 2.7.4 | 1 / 2 | |
| 2.7.3 | 1 / 2 | |
| 2.7.2 | 1 / 2 | |
| 2.7.1 | 1 / 2 |
v2.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.