@galacean/effects-plugin-stats MIT 80 versions

@galacean/effects-plugin-stats

npm

Galacean Effects runtime stats for the web

80

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.

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	2026/05/19
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	2026/05/14

Versions (showing 80 of 80)

Version	Deps	Published
2.9.3	0 / 1	2026-06-29
2.9.2	0 / 1	2026-06-26
2.9.1	0 / 1	2026-05-29
2.9.0	0 / 1	2026-05-11
2.8.12	0 / 1	2026-04-28
2.8.11	0 / 1	2026-04-17
2.8.10	0 / 1	2026-03-20
2.8.9	0 / 1	2026-02-27
2.8.8	0 / 1	2026-02-04
2.8.7	0 / 1	2026-01-30
2.8.6	0 / 1	2026-01-19
2.8.5	0 / 1	2026-01-15
2.8.4	0 / 1	2026-01-09
2.8.3	0 / 1	2026-01-05
2.8.2	0 / 1	2025-12-25
2.8.1	0 / 1	2025-12-23
2.8.0	0 / 1	2025-12-18
2.7.5	0 / 1	2025-12-18
2.7.4	0 / 1	2025-11-25
2.7.3	0 / 1	2025-11-14
2.7.2	0 / 1	2025-11-10
2.7.1	0 / 1	2025-11-04
2.7.0	0 / 1	2025-10-28
2.6.9	0 / 1	2025-10-22
2.6.8	0 / 1	2025-10-17
2.6.7	0 / 1	2025-10-10
2.6.6	0 / 1	2025-09-10
2.6.5	0 / 1	2025-08-29
2.6.4	0 / 1	2025-08-26
2.6.3	0 / 1	2025-08-22
2.6.2	0 / 1	2025-08-18
2.6.1	0 / 1	2025-08-12
2.6.0	0 / 1	2025-07-29
2.5.6	0 / 1	2025-07-24
2.5.5	0 / 1	2025-07-21
2.5.4	0 / 1	2025-07-17
2.5.3	0 / 1	2025-07-11
2.5.2	0 / 1	2025-07-09
2.5.1	0 / 1	2025-07-04
2.5.0	0 / 1	2025-07-04
2.4.8	0 / 1	2025-06-27
2.4.7	0 / 1	2025-06-13
2.4.6	0 / 1	2025-06-06
2.4.5	0 / 1	2025-05-28
2.4.4	0 / 1	2025-05-28
2.4.3	0 / 1	2025-05-21
2.4.2	0 / 1	2025-05-16
2.4.1	0 / 1	2025-05-16
2.4.0	0 / 1	2025-05-14
2.3.8	0 / 1	2025-05-28
2.3.7	0 / 1	2025-05-16
2.3.6	0 / 1	2025-05-13
2.3.5	0 / 1	2025-05-12
2.3.4	0 / 1	2025-05-09
2.3.3	0 / 1	2025-04-18
2.3.2	0 / 1	2025-04-14
2.3.1	0 / 1	2025-04-03
2.3.0	0 / 1	2025-04-02
2.2.7	0 / 1	2025-02-28
2.2.6	0 / 1	2025-02-21
2.2.5	0 / 1	2025-02-14
2.2.4	0 / 1	2025-02-07
2.2.3	0 / 1	2025-02-07
2.2.2	0 / 1	2025-01-13
2.2.1	0 / 1	2025-01-03
2.2.0	0 / 1	2024-12-31
2.1.5	0 / 1	2024-12-27
2.1.4	0 / 1	2024-12-20
2.1.3	0 / 1	2024-12-16
2.1.2	0 / 1	2024-11-29
2.1.1	0 / 1	2024-11-26
2.1.0	0 / 1	2024-11-20
2.0.7	0 / 1	2024-10-30
2.0.6	0 / 1	2024-09-13
2.0.5	0 / 1	2024-09-10
2.0.4	0 / 1	2024-08-30
2.0.3	0 / 1	2024-08-26
2.0.2	0 / 1	2024-08-23
2.0.1	0 / 1	2024-08-23
2.0.0	0 / 1	2024-08-21

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.