@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, 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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/config.js | AI (source-diff): Minified TypeScript build output; build script explicitly minifies dist/. Content is readable config-loading logic. | ai | |
| source-diff | obfuscated-file:dist/infra/regions.js | AI (source-diff): Minified build output; content is a static AWS region list with no suspicious behavior. | 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/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 | |
| 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/docker/DockerCli.build.js | AI (source-diff): Minified ESM output from documented build step; content is Docker CLI wrapper logic, 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 23 of 323)
| Version | Deps | Published |
|---|---|---|
| 0.2.0 | 2 / 3 | |
| 0.1.51 | 2 / 3 | |
| 0.1.49 | 2 / 3 | |
| 0.1.47 | 2 / 3 | |
| 0.1.46 | 2 / 3 | |
| 0.1.45 | 2 / 3 | |
| 0.1.44 | 2 / 3 | |
| 0.1.42 | 2 / 3 | |
| 0.1.40 | 2 / 3 | |
| 0.1.39 | 2 / 3 | |
| 0.1.38 | 2 / 3 | |
| 0.1.37 | 2 / 3 | |
| 0.1.36 | 2 / 3 | |
| 0.1.33 | 2 / 3 | |
| 0.1.32 | 2 / 3 | |
| 0.1.31 | 2 / 3 | |
| 0.1.30 | 2 / 4 | |
| 0.1.21 | 2 / 4 | |
| 0.1.20 | 2 / 4 | |
| 0.1.19 | 2 / 4 | |
| 0.1.18 | 2 / 4 | |
| 0.1.16 | 1 / 4 | |
| 0.1.10 | 0 / 3 |
v0.1.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.45
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.44
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.42
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.