@bpinternal/thicktoken
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/lite.js | AI (source-diff): Base64-embedded gzip merge table in bundler output, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/micro.js | AI (source-diff): Same wasmBase64 asset-embedding pattern from tsup bundling. | ai | |
| source-diff | obfuscated-file:dist/lite.mjs | AI (source-diff): Same wasmBase64 asset-embedding pattern from tsup bundling. | ai | |
| source-diff | obfuscated-file:dist/micro.mjs | AI (source-diff): Same wasmBase64 asset-embedding pattern from tsup bundling. | ai | |
| source-diff | encoded-string-file:dist/tokenizer.js | AI (source-diff): Base64 merge-table asset embedded by build, matches tokenizer's stated purpose. | ai | |
| source-diff | encoded-string-file:dist/tokenizer.mjs | AI (source-diff): Base64 merge-table asset embedded by build, matches tokenizer's stated purpose. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): WASM binary is the package's core tokenizer implementation (Rust→WASM), documented in description. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 0 / 6 | |
| 2.0.0 | 0 / 6 | |
| 1.2.1 | 0 / 6 | |
| 1.2.0 | 0 / 6 | |
| 1.1.0 | 0 / 6 |
v3.0.0
8 findingsPackage contains compiled binaries that could be backdoors: • wasm/pkg/thicktoken_wasm_bg.wasm
Newly 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.
Newly 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.
Modified file contains 2 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.