@iframe-resizer/core
Keep iframes sized to their content.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Legitimate scoped package @iframe-resizer/core; name similarity to 'cors' is coincidental, not squatting. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 5.5.9 | 1 / 0 | |
| 5.5.8 | 1 / 0 | |
| 5.5.7 | 1 / 0 | |
| 5.5.6 | 1 / 0 | |
| 5.5.5 | 1 / 0 | |
| 5.5.4 | 1 / 0 | |
| 5.5.3 | 1 / 0 | |
| 5.5.2 | 1 / 0 | |
| 5.5.1 | 1 / 0 | |
| 5.5.0 | 1 / 0 | |
| 5.4.7 | 1 / 0 |
v5.5.9
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.8
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.7
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.6
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.5
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.4
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.3
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.2
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.1
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.5.0
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.7
2 findingsPackage name '@iframe-resizer/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.