lerc
Rapid decoding of Lerc compressed raster data for any standard pixel type.
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): WASM codec is the package's core function (Esri LERC decoder), not a backdoor. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.1.2 | 0 / 0 | |
| 4.1.1 | 0 / 0 | |
| 4.1.0 | 0 / 0 | |
| 4.0.4 | 0 / 0 | |
| 4.0.3 | 0 / 0 | |
| 4.0.2 | 0 / 15 | |
| 4.0.1 | 0 / 0 | |
| 4.0.0 | 0 / 0 |
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
2 findingsPackage contains compiled binaries that could be backdoors: • lerc-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
2 findingsPackage contains compiled binaries that could be backdoors: • lerc-wasm.wasm • package/lerc-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
2 findingsPackage contains compiled binaries that could be backdoors: • dist/lerc-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
2 findingsPackage contains compiled binaries that could be backdoors: • lerc-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
2 findingsPackage contains compiled binaries that could be backdoors: • lerc-wasm.wasm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.