es-aggregate-error MIT 14 versions

es-aggregate-error

npm Repository Homepage

ES Proposal spec-compliant shim for AggregateError

14

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

ljharb

Keywords

AggregateErrorErroraggregateerrorsnativeerrores-shim APIshimpolyfill

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
publish-pattern	new-deps-added	AI (publish-pattern): New deps (define-data-property, set-function-name) are established es-shims/ljharb packages; routine refactoring pattern for this publisher's ecosystem.	ai	2026/04/24
dependencies	unvetted-dep:define-data-property	AI (dependencies): define-data-property is a standard es-shims/ljharb ecosystem package; it is a legitimate and expected dependency for this package.	ai	2026/04/23

Versions (showing 14 of 14)

Version	Deps	Published
1.0.14	8 / 15	2025-06-02
1.0.12	8 / 15	2024-02-05
1.0.11	8 / 15	2023-09-13
1.0.10	7 / 14	2023-08-27
1.0.9	7 / 15	2022-11-02
1.0.8	7 / 14	2022-05-05
1.0.7	6 / 13	2021-10-01
1.0.6	6 / 13	2021-10-01
1.0.5	6 / 13	2020-11-23
1.0.4	5 / 12	2020-08-09
1.0.3	5 / 11	2020-06-04
1.0.2	6 / 10	2019-12-14
1.0.1	6 / 9	2019-11-11
1.0.0	6 / 9	2019-10-21

v1.0.14

1 finding

LOW No provenance attestation provenance

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

v1.0.12

1 finding

LOW No provenance attestation provenance

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

v1.0.11

1 finding

LOW No provenance attestation provenance

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

v1.0.10

1 finding

LOW No provenance attestation provenance

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

v1.0.9

1 finding

LOW No provenance attestation provenance

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

v1.0.8

1 finding

LOW No provenance attestation provenance

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

v1.0.7

1 finding

LOW No provenance attestation provenance

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

v1.0.6

1 finding

LOW No provenance attestation provenance

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

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

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

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