@fuzdev/fuz_util
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:silent-process-exec | AI (semgrep): Fires on a documented spawn_detached utility helper; not malicious process execution. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Same spawn_detached helper; stable false positive for this utility package. | ai |
Versions (showing 46 of 46)
| Version | Deps | Published |
|---|---|---|
| 0.65.0 | 0 / 34 | |
| 0.64.0 | 0 / 34 | |
| 0.63.2 | 0 / 35 | |
| 0.63.1 | 0 / 35 | |
| 0.63.0 | 0 / 35 | |
| 0.62.0 | 0 / 35 | |
| 0.61.1 | 0 / 34 | |
| 0.61.0 | 0 / 34 | |
| 0.60.1 | 0 / 34 | |
| 0.60.0 | 0 / 34 | |
| 0.59.1 | 0 / 34 | |
| 0.59.0 | 0 / 34 | |
| 0.58.0 | 0 / 34 | |
| 0.57.0 | 0 / 34 | |
| 0.56.0 | 0 / 34 | |
| 0.55.0 | 0 / 34 | |
| 0.54.0 | 0 / 34 | |
| 0.53.4 | 0 / 32 | |
| 0.53.3 | 0 / 32 | |
| 0.53.2 | 0 / 32 | |
| 0.53.1 | 0 / 32 | |
| 0.53.0 | 0 / 32 | |
| 0.52.1 | 0 / 31 | |
| 0.52.0 | 0 / 31 | |
| 0.51.0 | 0 / 31 | |
| 0.50.1 | 0 / 27 | |
| 0.50.0 | 0 / 27 | |
| 0.49.3 | 0 / 27 | |
| 0.49.2 | 0 / 27 | |
| 0.49.1 | 0 / 27 | |
| 0.49.0 | 0 / 27 | |
| 0.48.4 | 0 / 26 | |
| 0.48.3 | 0 / 26 | |
| 0.48.2 | 0 / 26 | |
| 0.48.1 | 0 / 26 | |
| 0.48.0 | 0 / 26 | |
| 0.47.0 | 0 / 26 | |
| 0.46.0 | 0 / 26 | |
| 0.45.3 | 0 / 25 | |
| 0.45.2 | 0 / 25 | |
| 0.45.1 | 0 / 25 | |
| 0.45.0 | 0 / 25 | |
| 0.44.1 | 0 / 25 | |
| 0.44.0 | 0 / 25 | |
| 0.43.0 | 0 / 25 | |
| 0.42.0 | 0 / 25 |
v0.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.64.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.63.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.62.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.61.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.60.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.59.0
3 findingsSilent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/fuzdev/fuz_util/blob/d73e2f8dc5e75fe846e841c68691f58cac3b0049/src/lib/process.ts#L571 569 | ): SpawnDetachedResult => { 570 | try { > 571 | const child = node_spawn_child_process(command, args, { 572 | stdio: 'ignore', 573 | ...options,
Silent detached process — runs invisibly in the background (reverse shells, miners) Source: https://github.com/fuzdev/fuz_util/blob/d73e2f8dc5e75fe846e841c68691f58cac3b0049/src/lib/process.ts#L571 569 | ): SpawnDetachedResult => { 570 | try { > 571 | const child = node_spawn_child_process(command, args, { 572 | stdio: 'ignore', 573 | ...options,
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.57.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.56.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.55.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.53.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.52.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.51.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.50.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.44.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.