@datastructures-js/heap MIT 16 versions

@datastructures-js/heap

npm Repository Homepage

Min/Max Heap & Heap Sort implementation in javascript

16

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

eyas-ranjous

Keywords

heapmin heapmin heap data structuremax heapmax heap data structureheap jsheap data structureheap es6heap sortheapify

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
typosquat	typosquat.levenshtein:hapi	AI (typosquat): Scoped heap data-structure package; Levenshtein match to 'hapi' is a false positive with no semantic relationship.	ai	2026/04/29

Versions (showing 16 of 16)

Version	Deps	Published
4.3.7	0 / 10	2025-10-12
4.3.6	0 / 10	2025-10-12
4.3.5	0 / 10	2025-08-27
4.3.3	0 / 10	2024-01-08
4.3.2	0 / 10	2023-06-20
4.3.1	0 / 10	2023-01-08
4.3.0	0 / 10	2023-01-08
4.2.2	0 / 10	2022-12-24
4.2.1	0 / 10	2022-12-23
4.2.0	0 / 10	2022-12-23
4.1.2	0 / 10	2022-09-05
4.1.1	0 / 10	2022-08-16
4.1.0	0 / 10	2022-05-30
4.0.2	0 / 10	2022-03-13
4.0.1	0 / 10	2022-03-09
4.0.0	0 / 10	2022-02-22

v4.3.3

1 finding

LOW No provenance attestation provenance

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

v4.3.2

1 finding

LOW No provenance attestation provenance

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

v4.3.1

1 finding

LOW No provenance attestation provenance

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

v4.3.0

1 finding

LOW No provenance attestation provenance

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

v4.2.2

1 finding

LOW No provenance attestation provenance

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

v4.2.1

1 finding

LOW No provenance attestation provenance

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

v4.2.0

1 finding

LOW No provenance attestation provenance

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

v4.1.2

1 finding

LOW No provenance attestation provenance

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

v4.1.1

1 finding

LOW No provenance attestation provenance

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

v4.1.0

1 finding

LOW No provenance attestation provenance

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

v4.0.2

1 finding

LOW No provenance attestation provenance

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

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

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