js-encoding-utils — Greenflagged

Miscellaneous Encoding Utilities for Crypto-related Objects in JavaScript

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

kurihara

Keywords

pemderbase64base64urles6

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/test.bundle.js	AI (source-diff): dist/test.bundle.js is a webpack-bundled karma test suite. The 'obfuscation' is standard webpack UMD boilerplate, not malicious code. Stable false positive for this package.	ai	2026/04/24
source-diff	net-exec-file:dist/test.bundle.js	AI (source-diff): Network+exec signal is triggered by webpack's dynamic require mechanism in the test bundle, not actual network-fetching malware. Standard webpack test artifact for this package.	ai	2026/04/24
phantom-deps	phantom-dep:@babel/runtime	AI (phantom-deps): @babel/runtime is a legitimate runtime dependency used by convention with @babel/plugin-transform-runtime; not directly imported but required at runtime.	ai	2026/04/24
phantom-deps	phantom-dep:@babel/plugin-transform-regenerator	AI (phantom-deps): Babel plugin loaded by convention via Babel config, not directly imported. Standard Babel ecosystem pattern.	ai	2026/04/24
source-diff	obfuscated-file:dist/jseu.bundle.js	AI (source-diff): dist/jseu.bundle.js is a standard webpack production bundle explicitly built by the package's build script. The sample shows readable function names and no malicious patterns — this is expected minified output.	ai	2026/04/24

Versions (showing 32 of 32)

Version	Deps	Published
0.7.3	0 / 17	2023-09-02
0.7.2	0 / 17	2023-09-02
0.7.1	0 / 17	2021-12-07
0.7.0	0 / 17	2021-12-07
0.6.6	0 / 18	2021-11-22
0.6.2	0 / 18	2020-10-16
0.6.1	0 / 18	2020-10-16
0.6.0	0 / 18	2020-10-16
0.5.6	0 / 30	2019-11-19
0.5.5	0 / 30	2019-11-19
0.5.4	0 / 30	2019-09-18
0.5.3	0 / 30	2019-08-14
0.5.2	0 / 31	2019-07-13
0.5.1	0 / 31	2019-06-05
0.5.0	1 / 31	2019-06-05
0.4.0	1 / 31	2019-05-03
0.3.6	1 / 31	2019-04-09
0.3.4	1 / 31	2019-02-26
0.3.3	1 / 31	2019-01-01
0.3.2	1 / 31	2019-01-01
0.3.1	2 / 30	2018-12-05
0.3.0	2 / 29	2018-11-21
0.2.8	2 / 23	2018-11-08
0.2.7	2 / 23	2018-10-12
0.2.6	2 / 23	2018-10-01
0.2.5	2 / 23	2018-09-30
0.2.4	2 / 23	2018-09-28
0.2.3	2 / 23	2018-09-21
0.2.2	2 / 22	2018-09-21
0.2.1	2 / 22	2018-09-21
0.2.0	2 / 22	2018-09-21
0.1.0	2 / 23	2018-09-21

v0.7.3

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.6

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.6

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.7

1 finding

LOW No provenance attestation provenance

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

v0.2.6

2 findings

HIGH New obfuscated file: dist/jseu.bundle.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.

v0.2.5

1 finding

LOW No provenance attestation provenance

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

v0.2.4

1 finding

LOW No provenance attestation provenance

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

v0.2.3

1 finding

LOW No provenance attestation provenance

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

v0.2.2

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

3 findings

HIGH New obfuscated file: dist/test.bundle.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 file with network + code execution: dist/test.bundle.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

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

v0.1.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.