element-resize-event MIT 16 versions

element-resize-event

npm Repository Homepage

Polyfill to make it easy to listen for element resize events

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

kylemathewseaglus

Keywords

element querieselement-queryeventresize

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): New publisher kylemathews is the original package author (matching package.json author field and GitHub repo owner). This is a legitimate author reclaiming their own package, not a hostile takeover.	ai	2026/04/23
publish-pattern	dormant-publish	AI (publish-pattern): Dormancy followed by original author resuming ownership is benign. Changes are limited to dev tooling (husky, prettier) with no runtime or security impact.	ai	2026/04/23

Versions (showing 16 of 16)

Version	Deps	Published
3.0.6	0 / 7	2021-05-30
3.0.3	0 / 4	2018-11-16
3.0.2	0 / 4	2018-11-06
3.0.1	0 / 4	2018-09-25
2.0.9	0 / 4	2017-03-22
2.0.8	0 / 4	2017-03-21
2.0.7	0 / 4	2016-09-12
2.0.6	0 / 4	2016-09-12
2.0.5	0 / 4	2016-05-16
2.0.4	0 / 1	2016-04-16
2.0.3	0 / 1	2015-03-13
2.0.2	0 / 1	2015-03-06
2.0.1	0 / 1	2015-02-20
2.0.0	0 / 0	2015-02-19
1.0.1	0 / 0	2014-10-22
1.0.0	0 / 0	2014-10-04

v3.0.6

2 findings

HIGH Publisher changed: eaglus → kylemathews (on 2021-05-30) provenance

This version was published by a different npm account than previous versions on 2021-05-30. 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.

v3.0.3

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.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: kylemathews → eaglus (on 2018-09-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-25. This could indicate a legitimate maintainer transition or an account compromise.

v2.0.9

1 finding

LOW No provenance attestation provenance

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

v2.0.8

1 finding

LOW No provenance attestation provenance

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

v2.0.7

1 finding

LOW No provenance attestation provenance

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

v2.0.6

1 finding

LOW No provenance attestation provenance

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

v2.0.5

1 finding

LOW No provenance attestation provenance

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

v2.0.4

1 finding

LOW No provenance attestation provenance

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

v2.0.3

1 finding

LOW No provenance attestation provenance

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

v2.0.0

1 finding

LOW No provenance attestation provenance

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