@cesdk/cesdk-js
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 | obfuscated-file:assets/core/worker-host-v1.75.0.js | AI (source-diff): Minified worker bundle is a recurring pattern in this SDK; not obfuscation for concealment. | ai | |
| source-diff | obfuscated-file:assets/core/worker-host-v1.75.1.js | AI (source-diff): IMG.LY SDK ships versioned minified worker bundles every release; this is expected build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:assets/core/worker-host-v1.74.2.js | AI (source-diff): Commercial SDK ships minified/bundled worker JS as standard build output; stable pattern across all versions. | ai | |
| source-diff | obfuscated-file:assets/core/worker-host-v1.74.1.js | AI (source-diff): CE.SDK ships minified worker bundles as part of its standard build; this is expected for every release. | ai | |
| source-diff | obfuscated-file:assets/core/worker-host-v1.74.0.js | AI (source-diff): CE.SDK ships versioned minified worker bundles in every release; this is expected build output, not obfuscation. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.75.1 | 1 / 0 | |
| 1.75.0 | 1 / 0 | |
| 1.74.2 | 1 / 0 | |
| 1.74.1 | 1 / 0 | |
| 1.74.0 | 1 / 0 | |
| 1.73.1 | 1 / 0 | |
| 1.73.0 | 1 / 0 | |
| 1.72.3 | 1 / 0 | |
| 1.72.2 | 1 / 0 | |
| 1.72.1 | 1 / 0 | |
| 1.72.0 | 1 / 0 |
v1.75.1
2 findingsNewly 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.
v1.75.0
2 findingsNewly 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.
v1.74.2
2 findingsNewly 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.
v1.74.1
2 findingsNewly 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.
v1.74.0
2 findingsNewly 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.
v1.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.