power-assert-formatter MIT 25 versions

power-assert-formatter

npm Repository Homepage

Power Assert output formatter

25

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-asserttesttestingassertassertion

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	net-exec-file:build/power-assert-formatter.js	AI (source-diff): Browserify UMD bundle of the library's own source for browser use; UMD boilerplate triggers false positive on global/window/self checks.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is from the Browserify browser bundle; expected for a package that ships a standalone browser build.	ai	2026/04/24
semgrep	semgrep:dynamic-require	AI (semgrep): Standard plugin/renderer loading pattern in lib/create.js; user-configured renderer names loaded via require().	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance; trusted long-standing publisher.	ai	2026/04/24

Versions (showing 25 of 25)

Version	Deps	Published
1.4.1	7 / 28	2016-07-05
1.4.0	7 / 27	2016-06-05
1.3.2	12 / 23	2015-12-11
1.3.1	12 / 23	2015-11-12
1.3.0	12 / 23	2015-11-07
1.2.0	11 / 24	2015-11-03
1.1.0	11 / 22	2015-09-14
1.0.2	11 / 22	2015-08-25
1.0.1	11 / 22	2015-07-11
1.0.0	11 / 21	2015-06-24
0.11.0	8 / 21	2015-04-18
0.10.2	8 / 17	2015-02-16
0.10.1	8 / 17	2014-11-11
0.10.0	9 / 17	2014-11-11
0.9.0	8 / 15	2014-09-02
0.8.0	8 / 15	2014-08-12
0.7.1	3 / 16	2014-05-13
0.7.0	3 / 16	2014-05-12
0.6.1	1 / 17	2014-04-10
0.6.0	1 / 17	2014-04-10
0.4.0	0 / 18	2014-03-27
0.3.3	0 / 18	2013-12-31
0.3.2	0 / 18	2013-12-29
0.3.1	0 / 18	2013-12-24
0.3.0	0 / 14	2013-12-23

v1.4.1

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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.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 file with network + code execution: build/power-assert-formatter.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.10.2

1 finding

LOW No provenance attestation provenance

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

v0.10.1

1 finding

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.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.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.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.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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.