@galacean/effects-plugin-stats
Galacean Effects runtime stats 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 — the axios compromise (March 2026) relied on exactly this gap.
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 Galacean ecosystem package with 154 versions; domain risk is theoretical and no other malicious signals present. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established plugin in the @galacean/effects suite; sparse metadata is a style choice, not a spam indicator. | ai |
Versions (showing 51 of 52)
| Version | Deps | Published |
|---|---|---|
| 2.9.1 | 0 / 1 | |
| 2.9.0 | 0 / 1 | |
| 2.8.12 | 0 / 1 | |
| 2.8.11 | 0 / 1 | |
| 2.8.10 | 0 / 1 | |
| 2.8.9 | 0 / 1 | |
| 2.8.8 | 0 / 1 | |
| 2.8.7 | 0 / 1 | |
| 2.8.6 | 0 / 1 | |
| 2.8.5 | 0 / 1 | |
| 2.8.4 | 0 / 1 | |
| 2.8.3 | 0 / 1 | |
| 2.8.2 | 0 / 1 | |
| 2.8.1 | 0 / 1 | |
| 2.8.0 | 0 / 1 | |
| 2.7.5 | 0 / 1 | |
| 2.7.4 | 0 / 1 | |
| 2.7.3 | 0 / 1 | |
| 2.7.2 | 0 / 1 | |
| 2.7.1 | 0 / 1 | |
| 2.7.0 | 0 / 1 | |
| 2.6.9 | 0 / 1 | |
| 2.6.8 | 0 / 1 | |
| 2.6.7 | 0 / 1 | |
| 2.6.6 | 0 / 1 | |
| 2.6.5 | 0 / 1 | |
| 2.6.4 | 0 / 1 | |
| 2.6.3 | 0 / 1 | |
| 2.6.2 | 0 / 1 | |
| 2.6.1 | 0 / 1 | |
| 2.6.0 | 0 / 1 | |
| 2.5.6 | 0 / 1 | |
| 2.5.5 | 0 / 1 | |
| 2.5.4 | 0 / 1 | |
| 2.5.3 | 0 / 1 | |
| 2.5.2 | 0 / 1 | |
| 2.5.1 | 0 / 1 | |
| 2.5.0 | 0 / 1 | |
| 2.4.8 | 0 / 1 | |
| 2.4.7 | 0 / 1 | |
| 2.4.6 | 0 / 1 | |
| 2.4.5 | 0 / 1 | |
| 2.4.4 | 0 / 1 | |
| 2.4.3 | 0 / 1 | |
| 2.4.2 | 0 / 1 | |
| 2.4.1 | 0 / 1 | |
| 2.4.0 | 0 / 1 | |
| 2.3.8 | 0 / 1 | |
| 2.3.7 | 0 / 1 | |
| 2.3.6 | 0 / 1 | |
| 2.3.5 | 0 / 1 |
v2.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.11
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.10
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.9
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.8
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.7
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.6
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.5
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.4
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.3
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.2
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.1
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.8.0
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.5
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.4
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.3
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.2
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.1
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.7.0
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.9
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.8
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.7
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.6
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.5
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.4
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.3
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.6
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.5
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.4
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.3
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.2
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.1
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.8
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.6
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.4
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.7
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.6
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.5
2 findingsMaintainer email '[email protected]' uses domain 'yufangjun.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.