@galacean/effects-plugin-spine
Galacean Effects player spine plugin
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): Established Ant Group package with 251 versions; domain risk is theoretical and not actionable given the org's track record. | ai | |
| provenance | no-provenance | AI (provenance): Large org package with consistent publishing history; lack of provenance is common and not a risk signal here. | ai |
Versions (showing 13 of 13)
| 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.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 | |
| 1.6.10 | 2 / 1 |
v2.9.3
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.