events-to-array ISC 8 versions

events-to-array

npm Repository Homepage

Put a bunch of emitted events in an array, for testing.

8

Versions

ISC

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

isaacs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:coverage/lcov-report/prettify.js	AI (source-diff): This is the well-known Google Code Prettify JS, auto-generated by tap/Istanbul LCOV HTML coverage reports. Minified by design; no runtime impact. Stable false positive for this package.	ai	2026/04/24
source-diff	source-size-tripled	AI (source-diff): Size increase is entirely due to coverage/ report artifacts accidentally included in the publish. No injected payload; stable false positive for this package.	ai	2026/04/24

Versions (showing 8 of 8)

Version	Deps	Published
2.0.3	0 / 2	2022-11-10
2.0.2	0 / 2	2022-11-10
2.0.1	0 / 2	2022-11-10
2.0.0	0 / 1	2022-11-10
1.1.2	0 / 1	2017-04-10
1.0.2	0 / 1	2015-03-12
1.0.1	0 / 1	2015-03-02
1.0.0	0 / 1	2015-03-02

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

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

2 findings

HIGH New obfuscated file: coverage/lcov-report/prettify.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.

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