postprocessing No license 50 versions

postprocessing

npm Repository Homepage

50

Versions

—

License

No

Install Scripts

Attested

Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures gitHead linked

Maintainers

vanruesc

Keywords

renderingimagefiltereffectcomposerpasspostprocessinggpgpurttrendertexturerendertargetthree

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:build/index.cjs	AI (source-diff): esbuild bundle output with intact banner/src comments, not obfuscation.	ai	2026/07/21
source-diff	obfuscated-file:build/index.js	AI (source-diff): esbuild ESM bundle; readable module structure, no obfuscation.	ai	2026/07/21
source-diff	source-size-tripled	AI (source-diff): Growth is bundled dist for a mature graphics library.	ai	2026/07/21
source-diff	obfuscated-file:build/postprocessing.mjs	AI (source-diff): esbuild bundle output with readable module structure; standard dist file.	ai	2026/07/21
source-diff	obfuscated-file:build/postprocessing.js	AI (source-diff): Rollup UMD build output with library banner; minified not obfuscated, stable for this package.	ai	2026/07/21

Versions (showing 50 of 150)

Version	Deps	Published
6.17.3	0 / 24	2020-09-05
6.17.2	0 / 24	2020-08-30
6.17.1	0 / 24	2020-08-20
6.17.0	0 / 22	2020-08-20
6.16.0	0 / 25	2020-07-06
6.15.1	0 / 25	2020-06-28
6.14.3	0 / 25	2020-06-19
6.14.2	0 / 25	2020-06-19
6.14.1	0 / 25	2020-06-17
6.14.0	0 / 25	2020-06-05
6.13.5	0 / 23	2020-05-06
6.13.4	0 / 23	2020-05-01
6.13.3	0 / 24	2020-04-10
6.13.2	0 / 24	2020-03-25
6.13.1	0 / 24	2020-03-25
6.13.0	0 / 24	2020-03-17
6.12.2	0 / 24	2020-03-07
6.12.1	0 / 24	2020-03-06
6.12.0	0 / 24	2020-03-02
6.11.0	0 / 25	2020-02-23
6.10.0	0 / 25	2020-01-17
6.9.0	0 / 23	2019-12-08
6.8.9	0 / 23	2019-11-18
6.8.8	0 / 23	2019-11-01
6.8.7	0 / 23	2019-10-30
6.8.6	0 / 23	2019-10-30
6.8.5	0 / 22	2019-10-17
6.8.4	0 / 22	2019-10-15
6.8.3	0 / 22	2019-10-06
6.8.2	0 / 22	2019-10-04
6.8.1	0 / 22	2019-10-02
6.8.0	0 / 22	2019-09-30
6.7.0	0 / 22	2019-09-09
6.6.1	0 / 23	2019-09-02
6.6.0	0 / 23	2019-08-09
6.5.1	0 / 23	2019-06-26
6.5.0	0 / 23	2019-06-01
6.4.0	0 / 23	2019-05-19
6.3.3	0 / 23	2019-05-11
6.3.2	0 / 23	2019-04-29
6.3.1	0 / 23	2019-04-27
6.3.0	0 / 23	2019-04-25
6.2.2	0 / 23	2019-04-22
6.2.1	0 / 23	2019-04-10
6.2.0	0 / 23	2019-04-10
6.1.1	0 / 23	2019-03-29
6.1.0	0 / 23	2019-03-29
6.0.2	0 / 23	2019-03-23
6.0.1	0 / 23	2019-03-04
6.0.0	0 / 23	2019-03-03

v6.17.3

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.17.2

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.17.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.17.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.16.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.15.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.14.3

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.14.2

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.14.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.14.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.13.5

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.13.4

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.13.3

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.13.2

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.13.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.13.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.12.2

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.12.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.12.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.11.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.10.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.9.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.9

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.8

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.7

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.6

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.5

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.4

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.3

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.2

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.8.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.7.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.6.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.6.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.5.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.5.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.4.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.3.3

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.3.2

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.3.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.3.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.2.2

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.2.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.2.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.1.1

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.1.0

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.0.2

2 findings

HIGH New obfuscated file: build/postprocessing.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.

v6.0.1

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.

v6.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.