iframe-resizer
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@iframe-resizer/child | AI (dependencies): First-party monorepo sub-package from the same author/project; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@iframe-resizer/jquery | AI (dependencies): First-party monorepo sub-package from the same author/project; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@iframe-resizer/parent | AI (dependencies): First-party monorepo sub-package from the same author/project; stable pattern across versions. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 5.5.9 | 3 / 0 | |
| 5.5.8 | 3 / 0 | |
| 5.5.7 | 3 / 0 | |
| 5.5.6 | 3 / 0 | |
| 5.5.5 | 3 / 0 | |
| 5.5.4 | 3 / 0 | |
| 5.5.3 | 3 / 0 | |
| 5.5.2 | 3 / 0 | |
| 5.5.1 | 3 / 0 | |
| 5.5.0 | 3 / 0 | |
| 5.4.7 | 3 / 0 | |
| 5.4.6 | 3 / 0 | |
| 5.4.5 | 3 / 0 | |
| 5.4.4 | 3 / 0 | |
| 5.4.3 | 3 / 0 | |
| 5.4.2 | 3 / 0 | |
| 5.4.1 | 3 / 0 | |
| 5.4.0 | 3 / 0 | |
| 5.3.3 | 3 / 0 | |
| 5.3.2 | 3 / 0 | |
| 5.3.1 | 3 / 0 | |
| 5.3.0 | 3 / 0 | |
| 5.2.6 | 3 / 0 | |
| 5.2.5 | 3 / 0 | |
| 5.2.4 | 3 / 0 | |
| 5.2.3 | 3 / 0 |
v5.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.