@parcel/optimizer-image MIT 49 versions

@parcel/optimizer-image

npm Repository Homepage

49

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

devongovett

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): @parcel/workers is a first-party Parcel monorepo package from the same publisher and namespace; adding it is expected and benign for this package.	ai	2026/04/24
npm-metadata	bundled-binaries	AI (npm-metadata): These are legitimate NAPI prebuilt binaries for a multi-platform image optimizer plugin, built via @napi-rs/cli. Expected and documented pattern for this package.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require in native.js selects the correct platform-specific .node binary — canonical NAPI multi-platform pattern, not arbitrary code loading.	ai	2026/04/24
dependencies	unvetted-dep:detect-libc	AI (dependencies): detect-libc is a well-known utility for distinguishing glibc vs musl Linux; its use here is expected for selecting the correct native binary variant.	ai	2026/04/24

Versions (showing 49 of 49)

Show 3 prereleases

Version	Deps	Published
2.16.4	5 / 0	2026-02-02
2.16.3	5 / 0	2025-12-06
2.16.2	5 / 0	2025-12-06
2.16.1	5 / 0	2025-11-05
2.16.0	5 / 0	2025-09-18
2.15.4	5 / 0	2025-06-20
2.15.3	5 / 0	2025-06-20
2.15.2	5 / 0	2025-05-25
2.15.1	5 / 0	2025-05-16
2.15.0	5 / 0	2025-05-12
2.14.4	5 / 0	2025-03-29
2.14.3	5 / 0	2025-03-29
2.14.2	5 / 0	2025-03-23
2.14.1	5 / 0	2025-03-19
2.14.0	5 / 0	2025-03-18
2.13.3	5 / 0	2024-12-16
2.13.2	5 / 0	2024-11-25
2.13.1	5 / 0	2024-11-25
2.13.0	5 / 0	2024-11-12
2.12.0	5 / 0	2024-02-28
2.11.0	5 / 0	2024-01-04
2.10.3	5 / 2	2023-11-15
2.10.2	5 / 2	2023-11-02
2.10.1	5 / 2	2023-10-24
2.10.0	5 / 2	2023-10-11
2.9.3	4 / 2	2023-06-25
2.9.2	4 / 2	2023-06-08
2.9.1	4 / 2	2023-05-27
2.9.0	4 / 2	2023-05-26
2.8.3	5 / 2	2023-01-18
2.8.2	5 / 2	2022-12-14
2.8.1	5 / 2	2022-12-08
2.8.0	5 / 2	2022-11-09
2.7.0	5 / 2	2022-08-03
2.6.2	5 / 2	2022-06-22
2.6.1	5 / 2	2022-06-17
2.6.0	5 / 2	2022-05-25
2.5.0	5 / 2	2022-04-21
2.4.1	5 / 2	2022-03-31
2.4.0	5 / 2	2022-03-22
2.3.2	5 / 2	2022-02-18
2.3.1	5 / 2	2022-02-10
2.3.0	5 / 2	2022-02-09
2.2.1	5 / 2	2022-01-17
2.2.0	5 / 2	2022-01-12
2.1.1	5 / 2	2022-01-06
2.1.0	5 / 2	2022-01-05
2.0.1	4 / 2	2021-11-08
2.0.0	3 / 2	2021-10-13

v2.16.4

1 finding

LOW No provenance attestation provenance

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

v2.16.3

1 finding

LOW No provenance attestation provenance

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

v2.16.2

1 finding

LOW No provenance attestation provenance

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

v2.16.1

1 finding

LOW No provenance attestation provenance

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

v2.16.0

1 finding

LOW No provenance attestation provenance

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

v2.15.4

1 finding

LOW No provenance attestation provenance

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

v2.15.3

1 finding

LOW No provenance attestation provenance

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

v2.15.2

1 finding

LOW No provenance attestation provenance

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

v2.15.1

1 finding

LOW No provenance attestation provenance

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

v2.15.0

1 finding

LOW No provenance attestation provenance

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

v2.14.4

1 finding

LOW No provenance attestation provenance

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

v2.14.3

1 finding

LOW No provenance attestation provenance

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

v2.14.2

1 finding

LOW No provenance attestation provenance

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

v2.14.1

1 finding

LOW No provenance attestation provenance

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

v2.14.0

1 finding

LOW No provenance attestation provenance

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

v2.13.3

1 finding

LOW No provenance attestation provenance

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

v2.13.2

1 finding

LOW No provenance attestation provenance

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

v2.13.1

1 finding

LOW No provenance attestation provenance

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

v2.13.0

1 finding

LOW No provenance attestation provenance

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

v2.11.0

1 finding

LOW No provenance attestation provenance

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

v2.10.2

1 finding

LOW No provenance attestation provenance

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

v2.7.0

1 finding

LOW No provenance attestation provenance

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

v2.6.1

1 finding

LOW No provenance attestation provenance

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

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.1.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.