@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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Versions (showing 100 of 716)
| Version | Deps | Published |
|---|---|---|
| 1.0.615 | 1 / 0 | |
| 1.0.614 | 1 / 0 | |
| 1.0.613 | 1 / 0 | |
| 1.0.612 | 1 / 0 | |
| 1.0.611 | 1 / 0 | |
| 1.0.610 | 1 / 0 | |
| 1.0.609 | 1 / 0 | |
| 1.0.608 | 1 / 0 | |
| 1.0.607 | 1 / 0 | |
| 1.0.606 | 1 / 0 | |
| 1.0.605 | 1 / 0 | |
| 1.0.604 | 1 / 0 | |
| 1.0.603 | 1 / 0 | |
| 1.0.602 | 1 / 0 | |
| 1.0.601 | 1 / 0 | |
| 1.0.600 | 1 / 0 | |
| 1.0.599 | 1 / 0 | |
| 1.0.598 | 1 / 0 | |
| 1.0.597 | 1 / 0 | |
| 1.0.596 | 1 / 0 | |
| 1.0.595 | 1 / 0 | |
| 1.0.594 | 1 / 0 | |
| 1.0.593 | 1 / 0 | |
| 1.0.592 | 1 / 0 | |
| 1.0.591 | 1 / 0 | |
| 1.0.590 | 1 / 0 | |
| 1.0.589 | 1 / 0 | |
| 1.0.588 | 1 / 0 | |
| 1.0.587 | 1 / 0 | |
| 1.0.586 | 1 / 0 | |
| 1.0.585 | 1 / 0 | |
| 1.0.584 | 1 / 0 | |
| 1.0.583 | 1 / 0 | |
| 1.0.582 | 1 / 0 | |
| 1.0.581 | 1 / 0 | |
| 1.0.580 | 1 / 0 | |
| 1.0.579 | 1 / 0 | |
| 1.0.578 | 1 / 0 | |
| 1.0.577 | 1 / 0 | |
| 1.0.576 | 1 / 0 | |
| 1.0.575 | 1 / 0 | |
| 1.0.574 | 1 / 0 | |
| 1.0.573 | 1 / 0 | |
| 1.0.572 | 1 / 0 | |
| 1.0.571 | 1 / 0 | |
| 1.0.570 | 1 / 0 | |
| 1.0.569 | 1 / 0 | |
| 1.0.568 | 1 / 0 | |
| 1.0.567 | 1 / 0 | |
| 1.0.566 | 1 / 0 | |
| 1.0.565 | 1 / 0 | |
| 1.0.564 | 1 / 0 | |
| 1.0.563 | 1 / 0 | |
| 1.0.562 | 1 / 0 | |
| 1.0.561 | 1 / 0 | |
| 1.0.560 | 1 / 0 | |
| 1.0.559 | 1 / 0 | |
| 1.0.558 | 1 / 0 | |
| 1.0.557 | 1 / 0 | |
| 1.0.556 | 1 / 0 | |
| 1.0.555 | 1 / 0 | |
| 1.0.554 | 1 / 0 | |
| 1.0.553 | 1 / 0 | |
| 1.0.552 | 1 / 0 | |
| 1.0.551 | 1 / 0 | |
| 1.0.550 | 1 / 0 | |
| 1.0.549 | 1 / 0 | |
| 1.0.548 | 1 / 0 | |
| 1.0.547 | 1 / 0 | |
| 1.0.546 | 1 / 0 | |
| 1.0.545 | 1 / 0 | |
| 1.0.544 | 1 / 0 | |
| 1.0.543 | 1 / 0 | |
| 1.0.542 | 1 / 0 | |
| 1.0.541 | 1 / 0 | |
| 1.0.540 | 1 / 0 | |
| 1.0.539 | 1 / 0 | |
| 1.0.538 | 1 / 0 | |
| 1.0.537 | 1 / 0 | |
| 1.0.536 | 1 / 0 | |
| 1.0.535 | 1 / 0 | |
| 1.0.534 | 1 / 0 | |
| 1.0.533 | 1 / 0 | |
| 1.0.532 | 1 / 0 | |
| 1.0.531 | 1 / 0 | |
| 1.0.530 | 1 / 0 | |
| 1.0.529 | 1 / 0 | |
| 1.0.528 | 1 / 0 | |
| 1.0.527 | 1 / 0 | |
| 1.0.526 | 1 / 0 | |
| 1.0.525 | 1 / 0 | |
| 1.0.524 | 1 / 0 | |
| 1.0.523 | 1 / 0 | |
| 1.0.522 | 1 / 0 | |
| 1.0.521 | 1 / 0 | |
| 1.0.520 | 1 / 0 | |
| 1.0.519 | 1 / 0 | |
| 1.0.518 | 1 / 0 | |
| 1.0.517 | 1 / 0 | |
| 1.0.516 | 1 / 0 |
v1.0.541
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.540
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.539
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.538
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.537
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.536
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.535
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.534
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.533
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.532
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.531
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.530
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.529
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.528
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.527
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.526
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.525
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.524
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.523
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.522
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.521
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.520
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.519
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.518
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.517
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.516
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.