empower MIT 37 versions

empower

npm Repository Homepage

Power Assert feature enhancer for assert function/object

37

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

twada

Keywords

power-assertassertassertiontesttesting

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:build/empower.js	AI (source-diff): build/empower.js is a standard Browserify UMD bundle, not obfuscation. This is the documented build output for browser compatibility.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is from adding a Browserify bundle (build/empower.js) that inlines deps for browser use. Expected for this package.	ai	2026/04/24
source-diff	net-exec-file:test/buster_assertions_test.js	AI (source-diff): Standard UMD module wrapper in a test file; require() and define() calls are normal module loading, not malware. Stable FP for this package.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Legacy package predating Sigstore; trusted publisher with long track record. Informational only.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Dynamic require is in Gruntfile.js (dev-only build tooling), not in runtime library code. Standard Grunt test-loading pattern; no risk to package consumers.	ai	2026/04/24

Versions (showing 37 of 37)

Version	Deps	Published
1.3.1	2 / 21	2018-09-08
1.3.0	2 / 21	2018-06-12
1.2.3	2 / 21	2017-06-09
1.2.2	2 / 21	2017-06-03
1.2.1	2 / 21	2016-06-05
1.2.0	3 / 21	2016-05-31
1.1.0	8 / 21	2015-11-06
1.0.2	8 / 19	2015-10-22
1.0.1	7 / 19	2015-09-08
1.0.0	7 / 18	2015-05-25
0.11.0	2 / 18	2015-04-18
0.10.0	2 / 15	2014-11-11
0.9.1	2 / 15	2014-10-07
0.9.0	2 / 15	2014-09-01
0.8.0	2 / 15	2014-08-12
0.7.3	1 / 15	2014-06-29
0.7.2	1 / 17	2014-06-01
0.7.1	0 / 17	2014-05-08
0.7.0	0 / 17	2014-05-02
0.6.0	0 / 17	2014-04-10
0.4.1	0 / 17	2014-03-30
0.4.0	0 / 17	2014-03-27
0.3.5	0 / 17	2014-03-24
0.3.4	0 / 17	2014-01-05
0.3.3	0 / 16	2013-12-31
0.3.2	0 / 16	2013-12-24
0.3.1	0 / 16	2013-12-24
0.3.0	0 / 12	2013-12-23
0.2.1	0 / 8	2013-12-05
0.2.0	0 / 8	2013-12-04
0.1.6	0 / 7	2013-09-27
0.1.5	0 / 8	2013-09-14
0.1.4	0 / 8	2013-09-06
0.1.3	0 / 8	2013-08-30
0.1.2	0 / 7	2013-08-27
0.1.1	0 / 7	2013-08-25
0.1.0	0 / 7	2013-08-21

v1.3.1

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

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

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

1 finding

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

1 finding

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.

v0.11.0

2 findings

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

1 finding

LOW No provenance attestation provenance

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

v0.9.1

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

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

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

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

2 findings

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

1 finding

LOW No provenance attestation provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

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.