@xenova/transformers
State-of-the-art Machine Learning for the web. Run 🤗 Transformers directly in your browser, with no need for a server!
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New deps (jimp, onnxruntime-node) are established packages aligned with transformers.js functionality; no suspicious patterns. | ai | |
| dependencies | unvetted-dep:jimp | AI (dependencies): jimp is a standard image processing library; reasonable addition for transformers image handling. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is legitimate image data processing in transformers pipeline, not payload obfuscation. | ai | |
| dependencies | unvetted-dep:onnxruntime-node | AI (dependencies): onnxruntime-node is Microsoft's official ONNX Runtime Node.js binding, expected and appropriate for an ML inference library like transformers.js. Listed as optional dep, browser-excluded. | ai | |
| dependencies | unvetted-dep:sharp | AI (dependencies): sharp is a canonical image processing library; its use in transformers.js is legitimate and expected for ML workflows. | ai | |
| dependencies | unvetted-dep:onnxruntime-web | AI (dependencies): onnxruntime-web is Microsoft's official ONNX Runtime for browser inference — the core inference engine for transformers.js. Its use is fundamental and expected. | ai | |
| provenance | no-provenance | AI (provenance): Established package with clean history; provenance absence is acceptable for this publisher's track record. | ai |
Versions (showing 70 of 70)
| Version | Deps | Published |
|---|---|---|
| 2.17.2 | 3 / 11 | |
| 2.17.1 | 3 / 11 | |
| 2.17.0 | 3 / 11 | |
| 2.16.1 | 3 / 11 | |
| 2.16.0 | 3 / 11 | |
| 2.15.1 | 3 / 11 | |
| 2.15.0 | 3 / 11 | |
| 2.14.2 | 3 / 11 | |
| 2.14.1 | 3 / 11 | |
| 2.14.0 | 3 / 11 | |
| 2.13.4 | 3 / 11 | |
| 2.13.3 | 3 / 11 | |
| 2.13.2 | 3 / 11 | |
| 2.13.1 | 3 / 11 | |
| 2.13.0 | 3 / 11 | |
| 2.12.1 | 3 / 11 | |
| 2.12.0 | 2 / 11 | |
| 2.11.0 | 2 / 11 | |
| 2.10.1 | 2 / 11 | |
| 2.10.0 | 2 / 11 | |
| 2.9.0 | 2 / 11 | |
| 2.8.0 | 2 / 11 | |
| 2.7.0 | 2 / 11 | |
| 2.6.2 | 2 / 11 | |
| 2.6.1 | 2 / 11 | |
| 2.6.0 | 2 / 11 | |
| 2.5.4 | 3 / 11 | |
| 2.5.3 | 3 / 11 | |
| 2.5.2 | 3 / 11 | |
| 2.5.1 | 3 / 11 | |
| 2.5.0 | 3 / 11 | |
| 2.4.4 | 3 / 11 | |
| 2.4.3 | 3 / 11 | |
| 2.4.2 | 3 / 11 | |
| 2.4.1 | 3 / 11 | |
| 2.4.0 | 3 / 11 | |
| 2.3.1 | 3 / 11 | |
| 2.3.0 | 3 / 11 | |
| 2.2.0 | 3 / 10 | |
| 2.1.1 | 3 / 10 | |
| 2.1.0 | 3 / 10 | |
| 2.0.2 | 3 / 10 | |
| 2.0.1 | 3 / 10 | |
| 2.0.0 | 3 / 10 | |
| 1.4.3 | 3 / 5 | |
| 1.4.2 | 3 / 5 | |
| 1.4.1 | 3 / 5 | |
| 1.4.0 | 3 / 5 | |
| 1.3.5 | 3 / 4 | |
| 1.3.4 | 3 / 4 | |
| 1.3.3 | 3 / 4 | |
| 1.3.2 | 3 / 4 | |
| 1.3.1 | 2 / 4 | |
| 1.3.0 | 2 / 4 | |
| 1.2.6 | 2 / 4 | |
| 1.2.5 | 2 / 4 | |
| 1.2.4 | 2 / 4 | |
| 1.2.3 | 2 / 4 | |
| 1.2.2 | 2 / 4 | |
| 1.2.1 | 2 / 4 | |
| 1.2.0 | 2 / 4 | |
| 1.1.1 | 1 / 4 | |
| 1.1.0 | 1 / 4 | |
| 1.0.6 | 1 / 4 | |
| 1.0.5 | 1 / 4 | |
| 1.0.4 | 1 / 4 | |
| 1.0.3 | 1 / 4 | |
| 1.0.2 | 1 / 4 | |
| 1.0.1 | 1 / 4 | |
| 1.0.0 | 1 / 4 |
v2.17.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.