element-resize-detector

Resize event emitter for elements.

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

wnr

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): lwnr → wnr is the same person; GitHub repo is github.com/wnr/element-resize-detector. Account rename/migration, not a takeover.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from lwnr to wnr is same person (matches GitHub repo owner). Stable for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): wnr is the original author under a different npm handle; not a new maintainer.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): lwnr was the old npm handle for the same person (wnr); removal is expected.	ai	2026/04/24

Versions (showing 41 of 41)

Version	Deps	Published
1.2.4	1 / 15	2021-12-14
1.2.3	1 / 15	2021-06-24
1.2.2	1 / 15	2021-02-26
1.2.1	1 / 15	2020-01-15
1.2.0	1 / 15	2018-12-05
1.1.16	1 / 15	2020-01-09
1.1.15	1 / 15	2019-02-06
1.1.14	1 / 15	2018-02-28
1.1.13	1 / 15	2018-01-19
1.1.12	1 / 15	2017-04-26
1.1.11	1 / 15	2017-03-19
1.1.10	1 / 19	2016-12-12
1.1.9	1 / 19	2016-09-27
1.1.8	1 / 19	2016-09-06
1.1.7	1 / 19	2016-08-10
1.1.6	1 / 21	2016-08-03
1.1.5	1 / 21	2016-07-02
1.1.4	1 / 21	2016-06-18
1.1.3	1 / 21	2016-06-06
1.1.2	1 / 21	2016-05-17
1.1.1	1 / 21	2016-05-07
1.1.0	1 / 21	2016-02-06
1.0.3	1 / 21	2015-11-09
1.0.2	1 / 21	2015-11-01
1.0.1	1 / 21	2015-10-26
1.0.0	1 / 21	2015-10-25
0.4.0	1 / 21	2015-10-14
0.3.7	1 / 21	2015-10-06
0.3.5	1 / 21	2015-09-28
0.3.4	1 / 21	2015-09-21
0.3.3	1 / 21	2015-05-12
0.3.2	1 / 21	2015-05-10
0.3.1	1 / 21	2015-04-13
0.3.0	1 / 22	2015-04-13
0.2.8	1 / 21	2015-04-08
0.2.5	0 / 21	2015-03-25
0.2.3	0 / 21	2015-03-23
0.2.2	0 / 21	2015-03-23
0.1.4	0 / 7	2015-02-02
0.1.1	0 / 7	2015-01-27
0.1.0	0 / 7	2015-01-27

v1.2.4

1 finding

LOW No provenance attestation provenance

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

v1.2.3

1 finding

LOW No provenance attestation provenance

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

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.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.16

1 finding

LOW No provenance attestation provenance

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

v1.1.15

1 finding

LOW No provenance attestation provenance

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

v1.1.14

1 finding

LOW No provenance attestation provenance

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

v1.1.13

1 finding

LOW No provenance attestation provenance

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

v1.1.12

1 finding

LOW No provenance attestation provenance

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

v1.1.11

1 finding

LOW No provenance attestation provenance

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

v1.1.10

1 finding

LOW No provenance attestation provenance

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

v1.1.9

1 finding

LOW No provenance attestation provenance

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

v1.1.8

1 finding

LOW No provenance attestation provenance

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

v1.1.7

1 finding

LOW No provenance attestation provenance

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

v1.1.6

1 finding

LOW No provenance attestation provenance

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

v1.1.5

1 finding

LOW No provenance attestation provenance

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

v1.1.4

1 finding

LOW No provenance attestation provenance

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

v1.1.3

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

1 finding

LOW No provenance attestation provenance

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

v1.1.1

1 finding

LOW No provenance attestation provenance

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

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.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. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.7

1 finding

LOW No provenance attestation provenance

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

v0.3.5

1 finding

LOW No provenance attestation provenance

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

v0.3.4

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.8

1 finding

LOW No provenance attestation provenance

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

v0.2.5

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (lwnr) were replaced by new maintainers (wnr). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: lwnr → wnr (on 2015-03-25) provenance

This version was published by a different npm account than previous versions on 2015-03-25. 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.2.3

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (lwnr) were replaced by new maintainers (wnr). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: lwnr → wnr (on 2015-03-23) provenance

This version was published by a different npm account than previous versions on 2015-03-23. 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.2.2

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (lwnr) were replaced by new maintainers (wnr). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: lwnr → wnr (on 2015-03-23) provenance

This version was published by a different npm account than previous versions on 2015-03-23. 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.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

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