@pi-r/jimp
Jimp V1 image constructor for E-mc.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established package with 62 versions and consistent repo; long gap followed by minor update is plausible maintenance resumption. | ai | |
| dependencies | unvetted-dep:@e-mc/core | AI (dependencies): Same-author internal framework dep from anpham6/pi-r2 monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@e-mc/image | AI (dependencies): Same-author internal framework dep from anpham6/pi-r2 monorepo; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@e-mc/types | AI (dependencies): Same-author internal framework dep from anpham6/pi-r2 monorepo; stable false positive for this package family. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Image processing plugin that shells out to external binaries (WebP, etc.); expected pattern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require resolves binary helper packages (e.g. webp-bin) by name; stable pattern for this image plugin. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 61 versions; no provenance is common and not a risk signal here. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 0.12.3 | 7 / 0 | |
| 0.12.2 | 7 / 0 | |
| 0.12.1 | 7 / 0 | |
| 0.12.0 | 7 / 0 | |
| 0.11.3 | 7 / 0 | |
| 0.11.2 | 7 / 0 | |
| 0.11.1 | 7 / 0 | |
| 0.11.0 | 7 / 0 | |
| 0.10.5 | 5 / 0 | |
| 0.10.4 | 5 / 0 | |
| 0.10.3 | 5 / 0 | |
| 0.10.2 | 5 / 0 | |
| 0.10.1 | 5 / 0 | |
| 0.10.0 | 5 / 0 | |
| 0.9.6 | 5 / 0 | |
| 0.9.5 | 5 / 0 | |
| 0.9.4 | 5 / 0 | |
| 0.9.3 | 5 / 0 | |
| 0.9.2 | 5 / 0 | |
| 0.9.1 | 5 / 0 | |
| 0.9.0 | 5 / 0 | |
| 0.8.6 | 5 / 0 | |
| 0.8.5 | 5 / 0 | |
| 0.8.4 | 5 / 0 | |
| 0.8.3 | 5 / 0 | |
| 0.8.2 | 5 / 0 | |
| 0.8.1 | 5 / 0 | |
| 0.8.0 | 5 / 0 | |
| 0.7.7 | 5 / 0 | |
| 0.7.6 | 5 / 0 | |
| 0.7.5 | 5 / 0 | |
| 0.7.4 | 5 / 0 | |
| 0.7.3 | 5 / 0 | |
| 0.7.2 | 5 / 0 | |
| 0.7.1 | 5 / 0 | |
| 0.7.0 | 5 / 0 | |
| 0.6.11 | 5 / 0 | |
| 0.6.10 | 5 / 0 | |
| 0.6.9 | 5 / 0 | |
| 0.6.8 | 5 / 0 | |
| 0.6.7 | 5 / 0 | |
| 0.6.6 | 5 / 0 | |
| 0.6.5 | 5 / 0 | |
| 0.6.2 | 5 / 0 | |
| 0.6.0 | 5 / 0 | |
| 0.5.7 | 5 / 0 | |
| 0.5.6 | 5 / 0 | |
| 0.5.5 | 5 / 0 | |
| 0.5.4 | 5 / 0 | |
| 0.5.3 | 5 / 0 | |
| 0.5.2 | 5 / 0 | |
| 0.5.0 | 5 / 0 | |
| 0.3.8 | 5 / 0 | |
| 0.3.7 | 5 / 0 | |
| 0.3.6 | 5 / 0 | |
| 0.3.5 | 5 / 0 | |
| 0.3.4 | 5 / 0 | |
| 0.3.3 | 5 / 0 | |
| 0.3.2 | 5 / 0 | |
| 0.3.1 | 5 / 0 | |
| 0.3.0 | 5 / 0 | |
| 0.2.14 | 5 / 0 | |
| 0.2.13 | 5 / 0 | |
| 0.2.12 | 5 / 0 | |
| 0.2.11 | 5 / 0 | |
| 0.2.10 | 5 / 0 | |
| 0.2.9 | 5 / 0 | |
| 0.2.8 | 5 / 0 | |
| 0.2.2 | 5 / 0 | |
| 0.2.1 | 5 / 0 | |
| 0.2.0 | 5 / 0 | |
| 0.1.0 | 5 / 0 | |
| 0.0.1 | 5 / 0 |
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.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.6.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
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.6.5
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.6.2
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.6.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.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
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.5.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.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.3
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.3.2
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.3.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.
v0.3.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.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.13
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. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.10
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.9
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.8
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.2
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.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.
v0.2.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.1.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.0.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.