← Home

selection-range

npm Repository Homepage

get or set the selction range, or cursor position, for contenteditable

4
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

tootallnatebmcmahen

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change tootallnate→bmcmahen occurred in 2014; repo URL in package.json matches bmcmahen's GitHub, confirming legitimate ownership transfer. ai
maintainer-change maintainer-added AI (maintainer-change): Maintainer addition of bmcmahen is consistent with the 2014 repo transfer; no malicious indicators present. ai
provenance missing-githead AI (provenance): Published in 2014 when gitHead was not consistently captured by npm tooling; not indicative of tampering. ai

Versions (showing 4 of 4)

Version Deps Published
1.1.0 1 / 0
1.0.1 1 / 0
1.0.0 1 / 0
0.0.3 1 / 0

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

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bmcmahen.

HIGH Publisher changed: tootallnate → bmcmahen (on 2015-02-01) provenance

This version was published by a different npm account than previous versions on 2015-02-01. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: bmcmahen.

HIGH Publisher changed: tootallnate → bmcmahen (on 2014-08-15) provenance

This version was published by a different npm account than previous versions on 2014-08-15. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v0.0.3

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.