lie — Greenflagged

A basic but performant promise implementation

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

cwmma

Keywords

liepromiseasyncaplus

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:dist/lie.setImmediate.min.js	AI (source-diff): Minified version of the same setImmediate polyfill. Same false-positive rationale: postMessage is not a network call, eval is spec-compliant. No malicious behavior present.	ai	2026/04/22
source-diff	net-exec-file:dist/lie.setImmediate.js	AI (source-diff): File is a setImmediate polyfill; 'network' APIs are browser messaging (postMessage/MessageChannel), not HTTP. eval() is spec-compliant setImmediate behavior for string handlers. No actual dropper/loader pattern.	ai	2026/04/22
source-diff	source-size-tripled	AI (source-diff): Size increase is entirely explained by the committed browserify test bundle (test/browser.js, 323KB). This is a dev artifact for browser testing, not an injected payload.	ai	2026/04/22
source-diff	net-exec-file:test/browser.js	AI (source-diff): test/browser.js is a browserify-generated test bundle (per the 'browser' npm script). The detected pattern is the standard browserify module loader, not malicious network/exec behavior.	ai	2026/04/22
phantom-deps	phantom-dep:inline-process-browser	AI (phantom-deps): inline-process-browser is a browserify transform plugin correctly declared and referenced in browserify.transform config; not directly imported by design.	ai	2026/04/22
phantom-deps	phantom-dep:es3ify	AI (phantom-deps): es3ify is a browserify transform plugin correctly declared and referenced in browserify.transform config; not directly imported by design.	ai	2026/04/22
phantom-deps	phantom-dep:unreachable-branch-transform	AI (phantom-deps): unreachable-branch-transform is a browserify transform plugin correctly declared and referenced in browserify.transform config; not directly imported by design.	ai	2026/04/22
typosquat	typosquat.levenshtein:vite	AI (typosquat): lie is a legitimate promise library name, not a typosquat; Levenshtein distance is a false positive here.	ai	2026/04/21
dependencies	unvetted-dep:immediate	AI (dependencies): immediate is a stable, pinned dependency (~3.0.5) with no known vulnerabilities; acceptable for this package.	ai	2026/04/21

Versions (showing 46 of 46)

Version	Deps	Published
3.3.0	1 / 18	2018-03-06
3.2.0	1 / 17	2018-01-29
3.1.1	1 / 17	2017-02-09
3.1.0	1 / 17	2016-07-27
3.0.4	4 / 9	2016-04-30
3.0.3	4 / 9	2016-04-30
3.0.2	4 / 9	2016-01-21
3.0.1	4 / 9	2015-08-06
3.0.0	4 / 9	2015-07-30
2.9.1	3 / 9	2015-05-27
2.9.0	3 / 9	2015-05-26
2.8.1	1 / 9	2015-01-07
2.8.0	1 / 9	2014-09-19
2.7.7	1 / 6	2014-07-01
2.7.6	1 / 6	2014-06-04
2.7.5	1 / 6	2014-06-04
2.7.4	1 / 6	2014-05-08
2.7.3	1 / 6	2014-05-05
2.7.2	1 / 6	2014-05-04
2.7.0	1 / 6	2014-05-02
2.6.0	1 / 6	2014-03-14
2.5.4	1 / 7	2014-03-10
2.5.3	1 / 7	2014-01-30
2.5.2	1 / 7	2014-01-12
2.5.1	1 / 7	2014-01-08
2.5.0	1 / 7	2014-01-08
2.4.0	1 / 7	2013-12-19
2.3.0	1 / 7	2013-10-31
2.2.1	1 / 6	2013-10-28
2.2.0	1 / 6	2013-10-28
2.1.0	1 / 6	2013-10-26
2.0.7	1 / 5	2013-10-24
2.0.6	1 / 5	2013-10-11
2.0.5	1 / 5	2013-10-01
2.0.3	1 / 5	2013-09-27
2.0.1	1 / 5	2013-09-25
2.0.0	1 / 5	2013-09-25
1.4.0	0 / 6	2013-09-22
1.3.0	0 / 6	2013-09-19
1.0.3	0 / 6	2013-08-31
1.0.0	0 / 6	2013-08-30
0.6.2	0 / 6	2013-08-17
0.6.1	0 / 6	2013-08-17
0.6.0	0 / 6	2013-08-17
0.5.1	0 / 5	2013-08-17
0.5.0	0 / 5	2013-08-16

v3.2.0

1 finding

LOW No provenance attestation provenance

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

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

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

v3.0.4

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.

v3.0.3

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.

v3.0.2

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.

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

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

v2.9.1

2 findings

HIGH New file with network + code execution: test/browser.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.

v2.9.0

2 findings

HIGH New file with network + code execution: test/browser.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.

v2.8.1

2 findings

HIGH New file with network + code execution: test/browser.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.

v2.8.0

2 findings

HIGH New file with network + code execution: test/browser.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.

v2.7.7

1 finding

LOW No provenance attestation provenance

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

v2.7.6

1 finding

LOW No provenance attestation provenance

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

v2.7.5

1 finding

LOW No provenance attestation provenance

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

v2.7.4

1 finding

LOW No provenance attestation provenance

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

v2.7.3

1 finding

LOW No provenance attestation provenance

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

v2.7.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.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.4

1 finding

LOW No provenance attestation provenance

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

v2.5.3

1 finding

LOW No provenance attestation provenance

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

v2.5.2

1 finding

LOW No provenance attestation provenance

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

v2.5.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.

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

v2.3.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.

v2.2.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.

v2.2.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.

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

v2.0.7

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.

v2.0.6

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.

v2.0.5

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.

v2.0.3

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.

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

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.

v1.4.0

1 finding

LOW No provenance attestation provenance

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

v1.3.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.3

3 findings

HIGH New file with network + code execution: dist/lie.setImmediate.js source-diff

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

HIGH New file with network + code execution: dist/lie.setImmediate.min.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.

v1.0.0

3 findings

HIGH New file with network + code execution: dist/lie.setImmediate.js source-diff

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

HIGH New file with network + code execution: dist/lie.setImmediate.min.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.6.2

3 findings

HIGH New file with network + code execution: dist/lie.setImmediate.js source-diff

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

HIGH New file with network + code execution: dist/lie.setImmediate.min.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.6.1

3 findings

HIGH New file with network + code execution: dist/lie.setImmediate.js source-diff

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

HIGH New file with network + code execution: dist/lie.setImmediate.min.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.6.0

3 findings

HIGH New file with network + code execution: dist/lie.setImmediate.js source-diff

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

HIGH New file with network + code execution: dist/lie.setImmediate.min.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.5.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.

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