← Home

@galacean/effects-webgl

npm

Galacean Effects runtime webgl for the web

81
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

yiqiimchenjianchengkong.zxxeyworldwideyinjieruimeng.sugl3336563zhanyingweizhuxudongjohanzhumrkou47husongluzhuangjujiegujinyue1010feyabibi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
email-domain unclaimed-email:yufangjun.com AI (email-domain): Ant Group org package with long track record; individual contributor email domain risk is low for an org-published package. ai

Versions (showing 81 of 81)

Version Deps Published
2.9.3 1 / 0
2.9.2 1 / 0
2.9.1 1 / 0
2.9.0 1 / 0
2.8.12 1 / 0
2.8.11 1 / 0
2.8.10 1 / 0
2.8.9 1 / 0
2.8.8 1 / 0
2.8.7 1 / 0
2.8.6 1 / 0
2.8.5 1 / 0
2.8.4 1 / 0
2.8.3 1 / 0
2.8.2 1 / 0
2.8.1 1 / 0
2.8.0 1 / 0
2.7.5 1 / 0
2.7.4 1 / 0
2.7.3 1 / 0
2.7.2 1 / 0
2.7.1 1 / 0
2.7.0 1 / 0
2.6.9 1 / 0
2.6.8 1 / 0
2.6.7 1 / 0
2.6.6 1 / 0
2.6.5 1 / 0
2.6.4 1 / 0
2.6.3 1 / 0
2.6.2 1 / 0
2.6.1 1 / 0
2.6.0 1 / 0
2.5.6 1 / 0
2.5.5 1 / 0
2.5.4 1 / 0
2.5.3 1 / 0
2.5.2 1 / 0
2.5.1 1 / 0
2.5.0 1 / 0
2.4.8 1 / 0
2.4.7 1 / 0
2.4.6 1 / 0
2.4.5 1 / 0
2.4.4 1 / 0
2.4.3 1 / 0
2.4.2 1 / 0
2.4.1 1 / 0
2.4.0 1 / 0
2.3.8 1 / 0
2.3.7 1 / 0
2.3.6 1 / 0
2.3.5 1 / 0
2.3.4 1 / 0
2.3.3 1 / 0
2.3.2 1 / 0
2.3.1 1 / 0
2.3.0 1 / 0
2.2.7 2 / 0
2.2.6 2 / 0
2.2.5 2 / 0
2.2.4 2 / 0
2.2.3 2 / 0
2.2.2 2 / 0
2.2.1 2 / 0
2.2.0 2 / 0
2.1.5 2 / 0
2.1.4 2 / 0
2.1.3 2 / 0
2.1.2 2 / 0
2.1.1 2 / 0
2.1.0 2 / 0
2.0.7 2 / 0
2.0.6 2 / 0
2.0.5 2 / 0
2.0.4 2 / 0
2.0.3 2 / 0
2.0.2 2 / 0
2.0.1 2 / 0
2.0.0 2 / 0
1.6.10 1 / 0

v2.9.3

1 finding
LOW No provenance attestation provenance

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

v2.3.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.

v2.3.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.

v2.3.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.

v2.3.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.

v2.2.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.

v2.2.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.

v2.2.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.

v2.2.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.

v2.2.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.

v2.2.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.

v2.2.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.

v2.2.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.

v2.1.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.

v2.1.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.

v2.1.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.

v2.1.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.

v2.1.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.

v2.1.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.

v2.0.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.

v2.0.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.

v2.0.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.

v2.0.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.

v2.0.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.

v2.0.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.

v2.0.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.

v2.0.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.