← Home

gm

npm Repository Homepage

GraphicsMagick and ImageMagick for node.js

7
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

aaron

Keywords

graphicsmagickimagegraphicsmagickimagemagickgmconvertidentifycompare

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher 'aaron' is the original author Aaron Heckmann matching the GitHub repo owner; change from 'rwky' in 2016 is a legitimate transition. ai
semgrep semgrep:child-process-import AI (semgrep): gm is a GraphicsMagick/ImageMagick CLI wrapper; child_process.spawn is its core mechanism for invoking gm/convert commands. ai
provenance no-provenance AI (provenance): Legacy package predating Sigstore; no provenance is expected for packages of this age. ai

Versions (showing 7 of 7)

Version Deps Published
1.25.1 4 / 1
1.25.0 4 / 1
1.24.0 4 / 1
1.23.1 4 / 2
1.23.0 4 / 2
1.22.0 3 / 2
1.21.1 3 / 2

v1.25.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.25.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.24.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.23.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.23.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.22.0

2 findings
HIGH Publisher changed: rwky → aaron (on 2016-04-07) provenance

This version was published by a different npm account than previous versions on 2016-04-07. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.21.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.