@imgly/plugin-ai-image-generation-web
AI image generation plugin for the CE.SDK editor
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): New publisher mirko314-imgly is part of the same @imgly org with 47 approved packages; routine maintainer transition. | ai | |
| source-diff | net-exec-file:dist/bytedance/index.mjs | AI (source-diff): Network calls are expected for an AI image generation provider plugin; no dynamic code execution pattern visible in sample. | ai | |
| source-diff | obfuscated-file:dist/bytedance/index.mjs | AI (source-diff): Minified provider bundle matching existing pattern (fal-ai, open-ai, etc.); code is readable asset-search logic, not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/eachlabs/index.mjs | AI (source-diff): Network calls are to the eachlabs AI API (expected for an AI image generation plugin); code execution is standard JS function calls, not eval/dynamic execution. False positive for this package. | ai | |
| source-diff | obfuscated-file:dist/eachlabs/index.mjs | AI (source-diff): IMG.LY ships minified/bundled dist files for all their CE.SDK plugins. The sample shows legitimate UI plugin code (panel registration, image selection, i18n), not obfuscation. | ai | |
| dependencies | unvetted-dep:@imgly/plugin-ai-generation-web | AI (dependencies): Same-org sibling package from IMG.LY GmbH, versioned in lockstep with this package. Normal monorepo dependency pattern; not a third-party risk. | ai | |
| provenance | no-provenance | AI (provenance): IMG.LY packages consistently lack Sigstore provenance; this is a stable characteristic of the publisher, not a per-version anomaly. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.75.1 | 1 / 11 | |
| 1.75.0 | 1 / 11 | |
| 1.74.2 | 1 / 11 | |
| 1.74.1 | 1 / 11 | |
| 1.74.0 | 1 / 11 | |
| 1.73.1 | 1 / 11 | |
| 1.73.0 | 1 / 11 | |
| 1.72.3 | 1 / 11 | |
| 1.72.2 | 1 / 11 | |
| 1.72.1 | 1 / 11 | |
| 1.72.0 | 1 / 11 | |
| 1.71.0 | 1 / 11 | |
| 1.70.1 | 1 / 11 | |
| 1.70.0 | 1 / 11 | |
| 1.69.0 | 1 / 11 | |
| 1.68.0 | 1 / 11 | |
| 0.2.17 | 1 / 11 | |
| 0.2.16 | 1 / 11 | |
| 0.2.15 | 1 / 11 | |
| 0.2.14 | 1 / 11 | |
| 0.2.12 | 0 / 12 | |
| 0.2.11 | 1 / 11 |
v1.75.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.75.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.74.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.73.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.73.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.72.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.71.0
4 findingsThis version was published by a different npm account than previous versions on 2026-03-19. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.1
4 findingsThis version was published by a different npm account than previous versions on 2026-03-13. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.0
4 findingsThis version was published by a different npm account than previous versions on 2026-03-09. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.17
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.16
2 findingsThis version was published by a different npm account than previous versions on 2026-01-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.15
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.