@ls-stack/utils
Universal TypeScript utilities for browser and Node.js
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): Package exports a runShellCmd utility; child_process use is the core purpose. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Spreading process.env to pass to spawned shell commands is standard and intentional here. | ai |
Versions (showing 100 of 104)
| Version | Deps | Published |
|---|---|---|
| 3.77.0 | 3 / 24 | |
| 3.76.0 | 3 / 24 | |
| 3.75.0 | 3 / 24 | |
| 3.74.0 | 3 / 24 | |
| 3.73.1 | 3 / 24 | |
| 3.73.0 | 3 / 24 | |
| 3.72.0 | 3 / 24 | |
| 3.71.1 | 3 / 24 | |
| 3.71.0 | 3 / 24 | |
| 3.70.0 | 3 / 24 | |
| 3.69.0 | 3 / 24 | |
| 3.68.0 | 3 / 24 | |
| 3.67.0 | 2 / 24 | |
| 3.66.0 | 2 / 24 | |
| 3.65.0 | 2 / 24 | |
| 3.63.0 | 2 / 24 | |
| 3.62.0 | 2 / 24 | |
| 3.61.0 | 2 / 24 | |
| 3.60.0 | 2 / 24 | |
| 3.59.0 | 2 / 24 | |
| 3.58.0 | 2 / 24 | |
| 3.57.0 | 2 / 24 | |
| 3.56.0 | 2 / 24 | |
| 3.55.0 | 2 / 24 | |
| 3.54.0 | 2 / 24 | |
| 3.53.0 | 2 / 24 | |
| 3.52.0 | 2 / 24 | |
| 3.51.0 | 2 / 24 | |
| 3.50.0 | 2 / 24 | |
| 3.49.1 | 2 / 24 | |
| 3.49.0 | 2 / 24 | |
| 3.48.0 | 2 / 24 | |
| 3.47.0 | 2 / 24 | |
| 3.46.0 | 2 / 24 | |
| 3.45.0 | 2 / 24 | |
| 3.44.1 | 2 / 24 | |
| 3.44.0 | 2 / 24 | |
| 3.43.0 | 2 / 24 | |
| 3.42.0 | 2 / 24 | |
| 3.41.0 | 2 / 24 | |
| 3.40.0 | 2 / 24 | |
| 3.39.0 | 2 / 24 | |
| 3.38.0 | 2 / 24 | |
| 3.37.0 | 2 / 24 | |
| 3.36.0 | 2 / 24 | |
| 3.35.0 | 2 / 24 | |
| 3.34.1 | 2 / 24 | |
| 3.34.0 | 2 / 24 | |
| 3.33.0 | 2 / 24 | |
| 3.32.0 | 2 / 24 | |
| 3.31.0 | 2 / 24 | |
| 3.30.1 | 2 / 24 | |
| 3.30.0 | 2 / 24 | |
| 3.29.0 | 2 / 24 | |
| 3.28.0 | 2 / 24 | |
| 3.27.2 | 2 / 24 | |
| 3.27.1 | 2 / 24 | |
| 3.27.0 | 2 / 24 | |
| 3.26.1 | 2 / 24 | |
| 3.26.0 | 2 / 24 | |
| 3.25.0 | 2 / 24 | |
| 3.24.1 | 2 / 24 | |
| 3.24.0 | 2 / 24 | |
| 3.23.0 | 2 / 24 | |
| 3.22.0 | 2 / 24 | |
| 3.21.0 | 2 / 24 | |
| 3.20.0 | 2 / 24 | |
| 3.19.0 | 2 / 24 | |
| 3.18.0 | 2 / 23 | |
| 3.17.1 | 2 / 23 | |
| 3.17.0 | 2 / 23 | |
| 3.16.0 | 2 / 23 | |
| 3.15.0 | 2 / 23 | |
| 3.14.0 | 2 / 23 | |
| 3.13.0 | 2 / 23 | |
| 3.12.3 | 2 / 23 | |
| 3.12.2 | 2 / 23 | |
| 3.12.1 | 2 / 23 | |
| 3.12.0 | 2 / 23 | |
| 3.11.2 | 2 / 23 | |
| 3.11.1 | 2 / 23 | |
| 3.11.0 | 2 / 23 | |
| 3.10.0 | 2 / 23 | |
| 3.9.1 | 2 / 23 | |
| 3.9.0 | 2 / 20 | |
| 3.8.0 | 2 / 20 | |
| 3.7.0 | 1 / 20 | |
| 3.6.0 | 1 / 20 | |
| 3.5.0 | 1 / 20 | |
| 3.4.0 | 0 / 20 | |
| 3.3.2 | 0 / 20 | |
| 3.3.1 | 0 / 20 | |
| 3.3.0 | 0 / 20 | |
| 3.2.10 | 0 / 20 | |
| 3.2.9 | 0 / 20 | |
| 3.2.7 | 0 / 20 | |
| 3.2.6 | 0 / 20 | |
| 3.2.5 | 0 / 20 | |
| 3.2.4 | 0 / 20 | |
| 3.2.3 | 0 / 20 |
v3.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.