@useragent-kit/smoldot
Optional browser Smoldot lifecycle helpers for @useragent-kit/sdk
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 | encoded-string-file:dist/vendored-chain-specs.js | AI (source-diff): Long strings are blockchain chain-spec JSON (boot nodes, genesis data); generated by documented update script, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/vendored-chain-specs.js | AI (source-diff): Long lines are JSON blockchain chain-spec data serialized as string literals, not obfuscated code. | ai | |
| source-diff | obfuscated-file:dist/vendored-chain-specs.d.ts | AI (source-diff): TypeScript declaration file mirrors the same chain-spec string data; not obfuscated code. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is entirely explained by the addition of vendored chain-spec JSON data files. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Intentional placeholder/namespace-reservation package; 0.0.0 is expected. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Explicit stub package with no code by design; all signals are expected for a namespace placeholder. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 0.0.17 | 2 / 3 | |
| 0.0.16 | 2 / 3 | |
| 0.0.11 | 2 / 3 | |
| 0.0.8 | 2 / 3 | |
| 0.0.7 | 1 / 3 | |
| 0.0.6 | 1 / 3 | |
| 0.0.5 | 1 / 0 | |
| 0.0.4 | 0 / 0 | |
| 0.0.3 | 0 / 0 | |
| 0.0.2 | 0 / 0 | |
| 0.0.1 | 0 / 0 | |
| 0.0.0 | 0 / 0 |
v0.0.17
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wpar.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: wpar.
Modified file contains 3 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.8
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.
v0.0.7
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.
v0.0.6
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.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.