highland No license 30 versions

highland

npm Repository Homepage

30

Versions

—

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

caolanjeromewvqvu

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): util-deprecate is a trivial, well-known utility dep, no exec/network behavior.	ai	2026/07/19
publish-pattern	dormant-publish	AI (publish-pattern): Long-lived widely used package with normal slow release cadence.	ai	2026/07/19

Versions (showing 30 of 30)

Version	Deps	Published
2.13.5	1 / 23	2019-07-31
2.13.4	1 / 23	2019-04-05
2.13.3	1 / 23	2019-02-20
2.13.2	1 / 23	2019-02-20
2.13.1	1 / 23	2019-02-15
2.13.0	1 / 24	2018-03-21
2.12.0	1 / 24	2018-03-12
2.11.1	1 / 23	2017-07-13
2.11.0	1 / 23	2017-06-18
2.10.5	1 / 23	2017-03-23
2.10.4	1 / 23	2017-03-21
2.10.3	1 / 23	2017-03-21
2.10.2	1 / 23	2017-02-07
2.10.1	1 / 23	2016-10-30
2.10.0	1 / 23	2016-09-07
2.9.0	1 / 23	2016-07-08
2.8.1	1 / 23	2016-05-06
2.8.0	1 / 23	2016-05-06
2.7.4	1 / 22	2016-04-08
2.7.3	1 / 22	2016-03-31
2.7.2	1 / 22	2016-03-24
2.7.1	1 / 22	2016-02-29
2.6.0	1 / 22	2016-01-06
2.5.1	0 / 21	2015-05-20
2.5.0	0 / 21	2015-05-04
2.4.0	0 / 19	2015-02-17
2.3.0	0 / 18	2015-01-08
2.2.0	0 / 18	2014-12-08
2.1.0	0 / 18	2014-11-24
2.0.0	0 / 18	2014-09-30

v2.13.4

1 finding

LOW No provenance attestation provenance

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

v2.13.3

1 finding

LOW No provenance attestation provenance

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

v2.13.2

1 finding

LOW No provenance attestation provenance

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

v2.13.1

1 finding

LOW No provenance attestation provenance

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

v2.13.0

1 finding

LOW No provenance attestation provenance

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

v2.12.0

1 finding

LOW No provenance attestation provenance

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

v2.11.1

1 finding

LOW No provenance attestation provenance

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

v2.11.0

1 finding

LOW No provenance attestation provenance

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

v2.10.5

1 finding

LOW No provenance attestation provenance

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

v2.10.4

1 finding

LOW No provenance attestation provenance

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

v2.10.3

1 finding

LOW No provenance attestation provenance

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

v2.10.2

1 finding

LOW No provenance attestation provenance

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

v2.10.1

1 finding

LOW No provenance attestation provenance

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

v2.10.0

1 finding

LOW No provenance attestation provenance

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

v2.9.0

1 finding

LOW No provenance attestation provenance

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

v2.8.1

1 finding

LOW No provenance attestation provenance

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

v2.8.0

1 finding

LOW No provenance attestation provenance

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

v2.7.4

1 finding

LOW No provenance attestation provenance

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

v2.7.3

1 finding

LOW No provenance attestation provenance

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

v2.7.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jeromew → vqvu (on 2016-03-24, known maintainer) provenance

This version was published by a different npm account (vqvu) than the most recent previously approved version (jeromew) on 2016-03-24, but vqvu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.7.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: jeromew → vqvu (on 2016-02-29, known maintainer) provenance

This version was published by a different npm account (vqvu) than the most recent previously approved version (jeromew) on 2016-02-29, but vqvu is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.6.0

1 finding

LOW No provenance attestation provenance

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

v2.5.1

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.0

2 findings

MEDIUM Publisher changed: caolan → jeromew (on 2015-01-08, unremoved on npm for 4210d) provenance

This version was published by a different npm account (jeromew) than the most recent previously approved version (caolan) on 2015-01-08. It has since remained available on npm for 4210 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v2.2.0

1 finding

LOW No provenance attestation provenance

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

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

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