@fjall/util
Common utility methods
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/docker/DockerCli.build.js | AI (source-diff): Minified ESM output from documented build step; content is Docker CLI wrapper logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/docker/DockerCli.daemon.js | AI (source-diff): Minified ESM output from documented build step; content is Docker daemon probe logic, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/docker/DockerCli.js | AI (source-diff): Minified ESM output from documented build step; content is Docker CLI class, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/mcpProtocol/index.js | AI (source-diff): Minified ESM output from documented build step; content is zod schema definitions for MCP protocol, no malicious patterns. | ai | |
| typosquat | typosquat.levenshtein:uuid | AI (typosquat): Scoped utility package @fjall/util; name similarity to uuid is coincidental, not impersonation. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-organizations | AI (phantom-deps): @aws-sdk/client-organizations is explicitly listed as a runtime dependency in package.json. | ai |
Versions (showing 70 of 276)
| Version | Deps | Published |
|---|---|---|
| 0.33.1 | 3 / 3 | |
| 0.33.0 | 3 / 3 | |
| 0.32.0 | 3 / 3 | |
| 0.31.1 | 3 / 3 | |
| 0.30.0 | 3 / 3 | |
| 0.29.4 | 3 / 3 | |
| 0.29.3 | 3 / 3 | |
| 0.29.2 | 3 / 3 | |
| 0.29.1 | 3 / 3 | |
| 0.29.0 | 3 / 3 | |
| 0.28.0 | 3 / 3 | |
| 0.27.13 | 3 / 3 | |
| 0.27.12 | 3 / 3 | |
| 0.27.11 | 3 / 3 | |
| 0.27.10 | 3 / 3 | |
| 0.27.9 | 3 / 3 | |
| 0.27.8 | 3 / 3 | |
| 0.27.7 | 3 / 3 | |
| 0.27.5 | 3 / 3 | |
| 0.27.3 | 3 / 3 | |
| 0.27.1 | 3 / 3 | |
| 0.26.12 | 3 / 3 | |
| 0.26.11 | 3 / 3 | |
| 0.26.10 | 3 / 3 | |
| 0.26.9 | 3 / 3 | |
| 0.26.8 | 3 / 3 | |
| 0.26.7 | 3 / 3 | |
| 0.26.6 | 3 / 3 | |
| 0.26.5 | 3 / 3 | |
| 0.26.4 | 3 / 3 | |
| 0.26.2 | 3 / 3 | |
| 0.26.1 | 3 / 3 | |
| 0.26.0 | 3 / 3 | |
| 0.25.1 | 3 / 3 | |
| 0.25.0 | 3 / 3 | |
| 0.24.0 | 3 / 3 | |
| 0.23.0 | 3 / 3 | |
| 0.22.0 | 3 / 3 | |
| 0.21.1 | 3 / 3 | |
| 0.21.0 | 3 / 3 | |
| 0.20.5 | 3 / 3 | |
| 0.20.3 | 3 / 3 | |
| 0.20.2 | 3 / 3 | |
| 0.20.1 | 3 / 3 | |
| 0.20.0 | 3 / 3 | |
| 0.19.1 | 3 / 3 | |
| 0.18.0 | 3 / 3 | |
| 0.17.0 | 3 / 3 | |
| 0.16.9 | 3 / 3 | |
| 0.16.8 | 3 / 3 | |
| 0.16.6 | 3 / 3 | |
| 0.16.5 | 3 / 3 | |
| 0.16.0 | 3 / 3 | |
| 0.15.0 | 3 / 3 | |
| 0.14.1 | 3 / 3 | |
| 0.13.0 | 3 / 3 | |
| 0.12.0 | 3 / 3 | |
| 0.11.0 | 3 / 3 | |
| 0.10.0 | 3 / 3 | |
| 0.9.0 | 3 / 3 | |
| 0.8.2 | 3 / 3 | |
| 0.8.0 | 2 / 3 | |
| 0.7.0 | 2 / 3 | |
| 0.6.0 | 2 / 3 | |
| 0.5.0 | 2 / 3 | |
| 0.4.0 | 2 / 3 | |
| 0.3.1 | 2 / 3 | |
| 0.3.0 | 2 / 3 | |
| 0.2.0 | 2 / 3 | |
| 0.1.51 | 2 / 3 |
v0.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.