@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 100 of 276)
| Version | Deps | Published |
|---|---|---|
| 0.73.2 | 1 / 3 | |
| 0.73.0 | 1 / 3 | |
| 0.72.0 | 1 / 3 | |
| 0.71.8 | 1 / 3 | |
| 0.71.7 | 1 / 3 | |
| 0.71.6 | 1 / 3 | |
| 0.71.4 | 1 / 3 | |
| 0.71.3 | 1 / 3 | |
| 0.71.2 | 1 / 3 | |
| 0.71.1 | 1 / 3 | |
| 0.71.0 | 1 / 3 | |
| 0.70.1 | 1 / 3 | |
| 0.70.0 | 1 / 3 | |
| 0.69.10 | 1 / 3 | |
| 0.69.9 | 1 / 3 | |
| 0.69.8 | 1 / 3 | |
| 0.69.7 | 1 / 3 | |
| 0.69.6 | 1 / 3 | |
| 0.69.4 | 1 / 3 | |
| 0.69.3 | 1 / 3 | |
| 0.69.2 | 1 / 3 | |
| 0.69.1 | 1 / 3 | |
| 0.69.0 | 1 / 3 | |
| 0.68.0 | 1 / 3 | |
| 0.67.0 | 1 / 3 | |
| 0.66.0 | 1 / 3 | |
| 0.65.0 | 1 / 3 | |
| 0.64.1 | 1 / 3 | |
| 0.64.0 | 1 / 3 | |
| 0.63.0 | 1 / 3 | |
| 0.62.0 | 1 / 3 | |
| 0.61.8 | 1 / 3 | |
| 0.61.7 | 1 / 3 | |
| 0.61.6 | 1 / 3 | |
| 0.61.5 | 1 / 3 | |
| 0.61.4 | 1 / 3 | |
| 0.61.3 | 1 / 3 | |
| 0.61.0 | 1 / 3 | |
| 0.60.1 | 1 / 3 | |
| 0.60.0 | 1 / 3 | |
| 0.59.7 | 1 / 3 | |
| 0.59.6 | 1 / 3 | |
| 0.59.5 | 1 / 3 | |
| 0.59.4 | 1 / 3 | |
| 0.59.3 | 1 / 3 | |
| 0.59.2 | 1 / 3 | |
| 0.59.1 | 1 / 3 | |
| 0.59.0 | 1 / 3 | |
| 0.58.11 | 1 / 3 | |
| 0.58.10 | 1 / 3 | |
| 0.58.9 | 1 / 3 | |
| 0.58.8 | 1 / 3 | |
| 0.58.7 | 1 / 3 | |
| 0.58.5 | 3 / 3 | |
| 0.57.0 | 3 / 3 | |
| 0.56.0 | 3 / 3 | |
| 0.55.1 | 3 / 3 | |
| 0.55.0 | 3 / 3 | |
| 0.54.0 | 3 / 3 | |
| 0.53.0 | 3 / 3 | |
| 0.52.0 | 3 / 3 | |
| 0.51.3 | 3 / 3 | |
| 0.51.2 | 3 / 3 | |
| 0.51.1 | 3 / 3 | |
| 0.51.0 | 3 / 3 | |
| 0.50.1 | 3 / 3 | |
| 0.50.0 | 3 / 3 | |
| 0.49.1 | 3 / 3 | |
| 0.49.0 | 3 / 3 | |
| 0.48.0 | 3 / 3 | |
| 0.47.2 | 3 / 3 | |
| 0.47.1 | 3 / 3 | |
| 0.47.0 | 3 / 3 | |
| 0.46.7 | 3 / 3 | |
| 0.46.5 | 3 / 3 | |
| 0.46.4 | 3 / 3 | |
| 0.46.3 | 3 / 3 | |
| 0.46.2 | 3 / 3 | |
| 0.46.0 | 3 / 3 | |
| 0.45.3 | 3 / 3 | |
| 0.45.2 | 3 / 3 | |
| 0.44.2 | 3 / 3 | |
| 0.44.1 | 3 / 3 | |
| 0.44.0 | 3 / 3 | |
| 0.43.2 | 3 / 3 | |
| 0.43.1 | 3 / 3 | |
| 0.43.0 | 3 / 3 | |
| 0.42.1 | 3 / 3 | |
| 0.41.1 | 3 / 3 | |
| 0.40.2 | 3 / 3 | |
| 0.40.1 | 3 / 3 | |
| 0.38.1 | 3 / 3 | |
| 0.37.0 | 3 / 3 | |
| 0.36.0 | 3 / 3 | |
| 0.35.4 | 3 / 3 | |
| 0.35.3 | 3 / 3 | |
| 0.35.2 | 3 / 3 | |
| 0.35.1 | 3 / 3 | |
| 0.35.0 | 3 / 3 | |
| 0.34.1 | 3 / 3 |
v0.73.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.70.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.69.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.68.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.66.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.65.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.64.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.62.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.61.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.60.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.59.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.58.5
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.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.53.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.52.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.51.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.50.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.49.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.48.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.47.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.46.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.45.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.44.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.43.1
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.41.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.40.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.