← Home

@galacean/effects-specification

16
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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): Established Ant Group package with long history; domain risk is latent, no active exploitation signal. ai
provenance no-provenance AI (provenance): Galacean packages consistently lack provenance; stable false positive for this package family. ai

Versions (showing 16 of 16)

Version Deps Published
2.8.1 0 / 12
2.8.0 0 / 12
2.7.2 0 / 12
2.7.1 0 / 12
2.7.0 0 / 12
2.6.0 0 / 12
2.5.1 0 / 12
2.5.0 0 / 12
2.4.0 0 / 12
2.3.1 0 / 12
2.3.0 0 / 12
2.2.0 0 / 12
2.1.0 0 / 12
2.0.2 0 / 12
2.0.1 0 / 12
2.0.0 0 / 12

v2.3.0

1 finding
INFO No provenance attestation provenance

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

v2.2.0

1 finding
INFO No provenance attestation provenance

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

v2.1.0

1 finding
INFO No provenance attestation provenance

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

v2.0.2

1 finding
INFO No provenance attestation provenance

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

v2.0.1

1 finding
INFO No provenance attestation provenance

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

v2.0.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.