@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 51 of 323)
| Version | Deps | Published |
|---|---|---|
| 2.32.0 | 2 / 5 | |
| 2.31.1 | 2 / 5 | |
| 2.30.3 | 2 / 5 | |
| 2.30.0 | 2 / 5 | |
| 2.29.0 | 2 / 5 | |
| 2.27.0 | 2 / 5 | |
| 2.25.0 | 2 / 5 | |
| 2.24.0 | 2 / 5 | |
| 2.23.1 | 2 / 5 | |
| 2.23.0 | 2 / 5 | |
| 2.22.1 | 2 / 5 | |
| 2.22.0 | 2 / 5 | |
| 2.21.0 | 2 / 5 | |
| 2.20.1 | 2 / 5 | |
| 2.20.0 | 2 / 5 | |
| 2.19.6 | 2 / 5 | |
| 2.19.5 | 2 / 5 | |
| 2.19.4 | 2 / 5 | |
| 2.19.3 | 2 / 5 | |
| 2.19.2 | 2 / 5 | |
| 2.19.1 | 2 / 5 | |
| 2.19.0 | 2 / 5 | |
| 2.18.3 | 2 / 5 | |
| 2.18.2 | 2 / 5 | |
| 2.18.1 | 2 / 5 | |
| 2.18.0 | 2 / 5 | |
| 2.17.0 | 2 / 5 | |
| 2.16.0 | 2 / 5 | |
| 2.15.0 | 2 / 5 | |
| 2.14.0 | 2 / 5 | |
| 2.13.0 | 2 / 5 | |
| 2.12.0 | 2 / 5 | |
| 2.11.1 | 2 / 5 | |
| 2.9.1 | 2 / 5 | |
| 2.9.0 | 2 / 5 | |
| 2.8.0 | 2 / 5 | |
| 2.7.1 | 2 / 5 | |
| 2.7.0 | 2 / 5 | |
| 2.6.0 | 2 / 5 | |
| 2.5.0 | 2 / 5 | |
| 2.4.8 | 2 / 5 | |
| 2.4.7 | 2 / 5 | |
| 2.4.5 | 2 / 5 | |
| 2.4.4 | 2 / 5 | |
| 2.4.3 | 2 / 5 | |
| 2.4.2 | 2 / 5 | |
| 2.4.1 | 2 / 5 | |
| 2.4.0 | 2 / 5 | |
| 2.3.0 | 2 / 5 | |
| 2.2.0 | 2 / 5 | |
| 2.1.1 | 2 / 5 |
v2.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.30.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (josephce) than the most recent previously approved version (peoram) on 2026-07-16, but josephce is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v2.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.