@imgly/plugin-ai-sticker-generation-web
AI sticker 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 | no-provenance | AI (provenance): IMG.LY commercial SDK packages consistently lack Sigstore provenance; this is a stable characteristic of the package ecosystem, not a risk indicator. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): IMG.LY uses a custom commercial license across all their SDK packages; this is expected and stable for this publisher. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.76.0 | 1 / 10 | |
| 1.75.1 | 1 / 10 | |
| 1.75.0 | 1 / 10 | |
| 1.74.2 | 1 / 10 | |
| 1.74.1 | 1 / 10 | |
| 1.74.0 | 1 / 10 | |
| 1.73.1 | 1 / 10 | |
| 1.73.0 | 1 / 10 | |
| 1.72.3 | 1 / 10 | |
| 1.72.2 | 1 / 10 | |
| 1.72.1 | 1 / 10 | |
| 1.72.0 | 1 / 10 | |
| 0.2.17 | 1 / 10 | |
| 0.2.16 | 1 / 10 | |
| 0.2.15 | 1 / 10 | |
| 0.2.14 | 1 / 10 | |
| 0.2.12 | 0 / 11 | |
| 0.2.11 | 1 / 10 |
v1.76.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.
v0.2.17
1 finding[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
1 finding[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. Consider requesting the maintainer enable provenance via CI/CD.
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.