tiktoken
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 | large-new-source-files | AI (source-diff): Encoder data files for tiktoken; expected package layout. | ai | |
| source-diff | obfuscated-file:encoders/cl100k_base.cjs | AI (source-diff): BPE vocab data table, not obfuscated code. | ai | |
| source-diff | obfuscated-file:encoders/cl100k_base.js | AI (source-diff): BPE vocab data table. | ai | |
| source-diff | obfuscated-file:encoders/p50k_edit.cjs | AI (source-diff): BPE vocab data table. | ai | |
| source-diff | obfuscated-file:encoders/p50k_edit.js | AI (source-diff): BPE vocab data table. | ai | |
| source-diff | obfuscated-file:encoders/p50k_base.cjs | AI (source-diff): BPE vocab data table. | ai | |
| source-diff | obfuscated-file:encoders/p50k_base.js | AI (source-diff): BPE vocab data table. | ai | |
| source-diff | obfuscated-file:encoders/gpt2.cjs | AI (source-diff): BPE vocab data table. | ai | |
| source-diff | obfuscated-file:encoders/r50k_base.cjs | AI (source-diff): BPE vocab data table. | ai | |
| source-diff | obfuscated-file:encoders/gpt2.js | AI (source-diff): BPE vocab data table. | ai | |
| source-diff | obfuscated-file:encoders/r50k_base.js | AI (source-diff): BPE vocab data table. | ai | |
| npm-metadata | bundled-binaries | AI (npm-metadata): WASM tokenizer artifacts are core to this package; stable across versions. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.0.22 | 0 / 0 | |
| 1.0.21 | 0 / 0 | |
| 1.0.20 | 0 / 0 | |
| 1.0.19 | 0 / 0 | |
| 1.0.18 | 0 / 0 | |
| 1.0.17 | 0 / 0 | |
| 1.0.16 | 0 / 0 | |
| 1.0.15 | 0 / 0 | |
| 1.0.8 | 0 / 0 | |
| 1.0.7 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v1.0.21
2 findingsPackage contains compiled binaries that could be backdoors: • lite/tiktoken_bg.wasm • tiktoken_bg.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.20
2 findingsPackage contains compiled binaries that could be backdoors: • lite/tiktoken_bg.wasm • tiktoken_bg.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.19
2 findingsPackage contains compiled binaries that could be backdoors: • lite/tiktoken_bg.wasm • tiktoken_bg.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
2 findingsPackage contains compiled binaries that could be backdoors: • lite/tiktoken_bg.wasm • tiktoken_bg.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.17
2 findingsPackage contains compiled binaries that could be backdoors: • lite/tiktoken_bg.wasm • tiktoken_bg.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
2 findingsPackage contains compiled binaries that could be backdoors: • lite/tiktoken_bg.wasm • tiktoken_bg.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.15
2 findingsPackage contains compiled binaries that could be backdoors: • lite/tiktoken_bg.wasm • tiktoken_bg.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
12 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.
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.
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.
This version was published by a different npm account (davidduong) than the most recent previously approved version (gmpetrov) on 2023-06-15. It has since remained available on npm for 1131 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
12 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.
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.
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.
This version was published by a different npm account (davidduong) than the most recent previously approved version (gmpetrov) on 2023-05-13. It has since remained available on npm for 1164 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.