← Home

pngjs2

npm Repository Homepage

PNG encoder/decoder in pure JS, supporting any bit size & interlace, async & sync with full test suite.

9
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

agatronic

Keywords

PNGdecoderencoderjs-pngnode-pngparserpngpng-jspng-parsepngjs

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:coverage/prettify.js AI (source-diff): File is the well-known Google Code Prettify syntax highlighter bundled by Istanbul into HTML coverage reports. Not malicious; stable false positive for this package. ai
source-diff obfuscated-file:coverage/lcov-report/prettify.js AI (source-diff): Same Google Code Prettify file in the lcov-report subdirectory, also an Istanbul coverage artifact. Not malicious; stable false positive for this package. ai

Versions (showing 9 of 9)

Version Deps Published
2.0.0 0 / 8
1.2.0 0 / 8
1.1.0 0 / 8
1.0.2 0 / 8
1.0.1 0 / 8
1.0.0 0 / 8
0.0.3 0 / 5
0.0.2 0 / 0
0.0.1 0 / 0

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.2.0

3 findings
HIGH New obfuscated file: coverage/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: coverage/lcov-report/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

3 findings
HIGH New obfuscated file: coverage/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: coverage/lcov-report/prettify.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

1 finding
LOW No provenance attestation provenance

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