@imgly/plugin-vectorizer-web
Vectorizer 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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@imgly/vectorizer | AI (dependencies): First-party IMG.LY dependency consistent with the package's vectorizer plugin purpose and org namespace pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): IMG.LY publishes plugins in lockstep with CE.SDK releases; gaps between SDK versions naturally cause dormancy. No material changes in this version vs prior. | ai | |
| provenance | no-provenance | AI (provenance): IMG.LY is an established commercial SDK vendor; lack of Sigstore provenance is consistent across their entire package portfolio and not a meaningful risk signal. | ai | |
| license | uncommon-license:SEE LICENSE IN LICENSE.md | AI (license): IMG.LY uses a proprietary/commercial license for their SDK plugins; this pattern is expected and stable across all their packages. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.76.0 | 1 / 8 | |
| 1.75.1 | 1 / 8 | |
| 1.75.0 | 1 / 8 | |
| 1.74.2 | 1 / 8 | |
| 1.74.1 | 1 / 8 | |
| 1.74.0 | 1 / 8 | |
| 1.73.1 | 1 / 8 | |
| 1.73.0 | 1 / 8 | |
| 1.72.3 | 1 / 8 | |
| 1.72.2 | 1 / 8 | |
| 1.72.1 | 1 / 8 | |
| 1.72.0 | 1 / 8 | |
| 1.71.0 | 1 / 8 | |
| 1.70.1 | 1 / 8 | |
| 1.70.0 | 1 / 8 | |
| 1.69.0 | 1 / 8 | |
| 1.68.0 | 1 / 8 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.72.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.71.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.70.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.68.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.