@iconify/collections
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
Versions (showing 51 of 152)
| Version | Deps | Published |
|---|---|---|
| 1.0.693 | 1 / 0 | |
| 1.0.692 | 1 / 0 | |
| 1.0.691 | 1 / 0 | |
| 1.0.690 | 1 / 0 | |
| 1.0.689 | 1 / 0 | |
| 1.0.688 | 1 / 0 | |
| 1.0.687 | 1 / 0 | |
| 1.0.686 | 1 / 0 | |
| 1.0.685 | 1 / 0 | |
| 1.0.684 | 1 / 0 | |
| 1.0.683 | 1 / 0 | |
| 1.0.682 | 1 / 0 | |
| 1.0.681 | 1 / 0 | |
| 1.0.680 | 1 / 0 | |
| 1.0.679 | 1 / 0 | |
| 1.0.678 | 1 / 0 | |
| 1.0.677 | 1 / 0 | |
| 1.0.676 | 1 / 0 | |
| 1.0.675 | 1 / 0 | |
| 1.0.674 | 1 / 0 | |
| 1.0.673 | 1 / 0 | |
| 1.0.672 | 1 / 0 | |
| 1.0.671 | 1 / 0 | |
| 1.0.670 | 1 / 0 | |
| 1.0.669 | 1 / 0 | |
| 1.0.668 | 1 / 0 | |
| 1.0.667 | 1 / 0 | |
| 1.0.666 | 1 / 0 | |
| 1.0.665 | 1 / 0 | |
| 1.0.664 | 1 / 0 | |
| 1.0.663 | 1 / 0 | |
| 1.0.662 | 1 / 0 | |
| 1.0.661 | 1 / 0 | |
| 1.0.660 | 1 / 0 | |
| 1.0.659 | 1 / 0 | |
| 1.0.658 | 1 / 0 | |
| 1.0.657 | 1 / 0 | |
| 1.0.656 | 1 / 0 | |
| 1.0.655 | 1 / 0 | |
| 1.0.654 | 1 / 0 | |
| 1.0.653 | 1 / 0 | |
| 1.0.652 | 1 / 0 | |
| 1.0.651 | 1 / 0 | |
| 1.0.650 | 1 / 0 | |
| 1.0.649 | 1 / 0 | |
| 1.0.648 | 1 / 0 | |
| 1.0.647 | 1 / 0 | |
| 1.0.646 | 1 / 0 | |
| 1.0.645 | 1 / 0 | |
| 1.0.644 | 1 / 0 | |
| 1.0.643 | 1 / 0 |
v1.0.693
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.692
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.691
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.690
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.689
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.688
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.687
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.686
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.685
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.684
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.683
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.682
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.681
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.680
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.679
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.678
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.676
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.675
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.674
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.673
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.672
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.671
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.670
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.669
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.668
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.667
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.666
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.665
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.662
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.658
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.656
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.652
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.647
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.