@soonspacejs/plugin-gs3d-loader No license 32 versions

@soonspacejs/plugin-gs3d-loader

npm

32

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

xuekjiangqiguobinyongchjxxococalijiahao9966

Keywords

soonspacejsgs3dLoader

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	encoded-string-file:dist/index.esm.js	AI (source-diff): Encoded string is a base64 WASM binary (AGFzbQ = WASM magic bytes); expected for a 3D geometry loader plugin.	ai	2026/05/09

Versions (showing 32 of 32)

Version	Deps	Published
2.15.8	0 / 0	2026-05-25
2.15.4	0 / 0	2026-04-27
2.15.1	0 / 0	2026-04-09
2.15.0	0 / 0	2026-04-09
2.14.37	0 / 0	2026-04-03
2.14.35	0 / 0	2026-04-01
2.14.34	0 / 0	2026-03-30
2.14.33	0 / 0	2026-03-30
2.14.32	0 / 0	2026-03-25
2.14.31	0 / 0	2026-03-24
2.14.30	0 / 0	2026-03-24
2.14.29	0 / 0	2026-02-06
2.14.28	0 / 0	2026-02-02
2.14.27	0 / 0	2026-01-21
2.14.26	0 / 0	2026-01-21
2.14.24	0 / 0	2026-01-14
2.14.23	0 / 0	2025-12-29
2.14.21	0 / 0	2025-12-29
2.14.13	0 / 0	2025-12-05
2.14.12	0 / 0	2025-11-19
2.14.11	0 / 0	2025-11-19
2.14.10	0 / 0	2025-10-13
2.14.9	0 / 0	2025-10-13
2.14.8	0 / 0	2025-09-28
2.14.7	0 / 0	2025-09-27
2.14.6	0 / 0	2025-09-27
2.14.5	0 / 0	2025-09-25
2.14.2	0 / 0	2025-09-20
2.14.1	0 / 0	2025-09-15
2.13.8	0 / 0	2025-07-16
2.13.7	0 / 0	2025-07-16
2.13.6	0 / 0	2025-07-16

v2.15.8

1 finding

LOW No provenance attestation provenance

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

v2.15.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.14.32

1 finding

LOW No provenance attestation provenance

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

v2.14.31

1 finding

LOW No provenance attestation provenance

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

v2.14.30

1 finding

LOW No provenance attestation provenance

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

v2.14.29

1 finding

LOW No provenance attestation provenance

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

v2.14.28

1 finding

LOW No provenance attestation provenance

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

v2.14.27

1 finding

LOW No provenance attestation provenance

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

v2.14.26

1 finding

LOW No provenance attestation provenance

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

v2.14.24

1 finding

LOW No provenance attestation provenance

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

v2.14.23

1 finding

LOW No provenance attestation provenance

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

v2.14.21

1 finding

LOW No provenance attestation provenance

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

v2.14.13

1 finding

LOW No provenance attestation provenance

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

v2.14.12

1 finding

LOW No provenance attestation provenance

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

v2.14.11

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.14.10

2 findings

HIGH Long encoded string in modified file: dist/index.esm.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.14.9

2 findings

HIGH Long encoded string in modified file: dist/index.esm.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.14.8

2 findings

HIGH Long encoded string in modified file: dist/index.esm.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.14.7

2 findings

HIGH Long encoded string in modified file: dist/index.esm.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.14.6

2 findings

HIGH Long encoded string in modified file: dist/index.esm.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.14.5

2 findings

HIGH Long encoded string in modified file: dist/index.esm.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.14.2

2 findings

HIGH Long encoded string in modified file: dist/index.esm.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.14.1

2 findings

HIGH Long encoded string in modified file: dist/index.esm.js source-diff

Modified file contains 4 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

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

v2.13.8

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.13.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.13.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.