shadow-cljs ISC 35 versions

shadow-cljs

npm Repository Homepage

ClojureScript compiler and JS bundler

35

Versions

ISC

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

thheller

Keywords

clojurescriptcljs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
semgrep	semgrep:child-process-import	AI (semgrep): CLI build tool that spawns JVM/node processes; child_process use is core to its function.	ai	2026/04/29
semgrep	semgrep:child-process-spawn	AI (semgrep): Spawning executables is the primary purpose of this CLI tool.	ai	2026/04/29
semgrep	semgrep:dynamic-require	AI (semgrep): runner.js loads project-local shadow-cljs version by design; documented behavior.	ai	2026/04/29
phantom-deps	phantom-dep:ws	AI (phantom-deps): Runtime dep used by compiled ClojureScript output, not directly imported in JS.	ai	2026/04/29
phantom-deps	phantom-dep:buffer	AI (phantom-deps): Runtime dep used by compiled ClojureScript output, not directly imported in JS.	ai	2026/04/29
phantom-deps	phantom-dep:process	AI (phantom-deps): Runtime dep used by compiled ClojureScript output, not directly imported in JS.	ai	2026/04/29
phantom-deps	phantom-dep:source-map-support	AI (phantom-deps): Runtime dep used by compiled ClojureScript output, not directly imported in JS.	ai	2026/04/29

Versions (showing 35 of 35)

Version	Deps	Published
3.4.11	7 / 0	2026-05-18
3.4.10	7 / 0	2026-05-12
3.4.9	7 / 0	2026-05-07
3.4.8	7 / 0	2026-05-07
3.4.7	7 / 0	2026-05-07
3.4.6	7 / 0	2026-04-28
3.4.5	7 / 0	2026-04-26
3.4.4	7 / 0	2026-04-15
3.4.2	7 / 0	2026-04-14
3.4.1	7 / 0	2026-04-12
3.4.0	7 / 0	2026-04-10
3.3.8	7 / 0	2026-03-31
3.3.7	7 / 0	2026-03-28
3.3.6	7 / 0	2026-02-12
3.3.5	7 / 0	2026-01-14
3.3.4	7 / 0	2025-12-13
3.3.3	7 / 0	2025-12-08
3.3.2	7 / 0	2025-11-29
3.3.1	7 / 0	2025-11-26
3.3.0	7 / 0	2025-11-26
3.2.2	7 / 0	2025-11-26
3.2.1	7 / 0	2025-09-23
3.2.0	7 / 0	2025-08-17
3.1.8	7 / 0	2025-07-24
3.1.7	7 / 0	2025-06-14
3.1.6	7 / 0	2025-06-11
3.1.5	7 / 0	2025-05-28
3.1.4	7 / 0	2025-05-22
3.1.3	7 / 0	2025-05-21
3.1.2	7 / 0	2025-05-20
3.1.1	7 / 0	2025-05-17
3.1.0	7 / 0	2025-05-17
3.0.6	7 / 0	2025-05-16
3.0.5	5 / 0	2025-05-07
3.0.4	5 / 0	2025-05-01

v3.4.11

1 finding

LOW No provenance attestation provenance

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

v3.4.10

1 finding

LOW No provenance attestation provenance

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

v3.4.9

1 finding

LOW No provenance attestation provenance

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

v3.4.8

1 finding

LOW No provenance attestation provenance

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

v3.4.7

1 finding

LOW No provenance attestation provenance

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

v3.4.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.

v3.4.5

1 finding

LOW No provenance attestation provenance

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

v3.4.4

1 finding

LOW No provenance attestation provenance

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

v3.4.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.

v3.4.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.

v3.4.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.

v3.3.8

1 finding

LOW No provenance attestation provenance

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

v3.3.7

1 finding

LOW No provenance attestation provenance

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

v3.3.6

1 finding

LOW No provenance attestation provenance

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

v3.3.5

1 finding

LOW No provenance attestation provenance

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

v3.3.4

1 finding

LOW No provenance attestation provenance

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

v3.3.3

1 finding

LOW No provenance attestation provenance

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

v3.3.2

1 finding

LOW No provenance attestation provenance

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

v3.3.1

1 finding

LOW No provenance attestation provenance

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

v3.3.0

1 finding

LOW No provenance attestation provenance

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

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.8

1 finding

LOW No provenance attestation provenance

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

v3.1.7

1 finding

LOW No provenance attestation provenance

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

v3.1.6

1 finding

LOW No provenance attestation provenance

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

v3.1.5

1 finding

LOW No provenance attestation provenance

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

v3.1.4

1 finding

LOW No provenance attestation provenance

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

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

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

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

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

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

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

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