heic-to
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 |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/csp/heic-to.js | AI (source-diff): Bundled Emscripten/libheif WASM worker code inlined as string; expected for this package. | ai | |
| source-diff | encoded-string-file:dist/heic-to.js | AI (source-diff): Bundled Emscripten/libheif WASM worker code inlined as string; expected for this package. | ai | |
| source-diff | encoded-string-file:dist/iife/heic-to.js | AI (source-diff): Bundled Emscripten/libheif WASM worker code inlined as string; expected for this package. | ai | |
| source-diff | encoded-string-file:dist/next/heic-to.js | AI (source-diff): Bundled Emscripten/libheif WASM worker code inlined as string; expected for this package. | ai | |
| source-diff | encoded-string-file:dist/csp/heic-to.min.js | AI (source-diff): Minified variant of the same bundled Emscripten output. | ai | |
| source-diff | encoded-string-file:dist/heic-to.min.js | AI (source-diff): Minified variant of the same bundled Emscripten output. | ai | |
| source-diff | encoded-string-file:src/lib/libheif-without-unsafe-eval.js | AI (source-diff): Emscripten-compiled libheif C library; expected for HEIC decoder. | ai | |
| source-diff | encoded-string-file:src/lib/libheif.js | AI (source-diff): Emscripten-compiled libheif C library; expected for HEIC decoder. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 1.5.2 | 0 / 2 | |
| 1.5.1 | 0 / 2 | |
| 1.5.0 | 0 / 2 | |
| 1.4.3 | 0 / 2 | |
| 1.4.2 | 0 / 2 |
v1.5.2
9 findingsModified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 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.
v1.5.1
9 findingsModified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 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.
v1.5.0
9 findingsModified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 34 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.
v1.4.3
9 findingsModified file contains 30 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 30 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 30 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 30 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 30 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 30 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 30 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Modified file contains 30 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.