@alfalab/icons-glyph
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 123)
| Version | Deps | Published |
|---|---|---|
| 2.288.0 | 0 / 0 | |
| 2.287.0 | 0 / 0 | |
| 2.286.0 | 0 / 0 | |
| 2.285.0 | 0 / 0 | |
| 2.284.0 | 0 / 0 | |
| 2.283.0 | 0 / 0 | |
| 2.282.0 | 0 / 0 | |
| 2.281.0 | 0 / 0 | |
| 2.280.0 | 0 / 0 | |
| 2.279.0 | 0 / 0 | |
| 2.278.0 | 0 / 0 | |
| 2.277.0 | 0 / 0 | |
| 2.276.0 | 0 / 0 | |
| 2.275.0 | 0 / 0 | |
| 2.274.0 | 0 / 0 | |
| 2.273.0 | 0 / 0 | |
| 2.272.0 | 0 / 0 | |
| 2.271.0 | 0 / 0 | |
| 2.270.0 | 0 / 0 | |
| 2.269.0 | 0 / 0 | |
| 2.268.0 | 0 / 0 | |
| 2.267.0 | 0 / 0 | |
| 2.266.0 | 0 / 0 | |
| 2.265.0 | 0 / 0 | |
| 2.264.0 | 0 / 0 | |
| 2.263.0 | 0 / 0 | |
| 2.262.0 | 0 / 0 | |
| 2.261.0 | 0 / 0 | |
| 2.260.0 | 0 / 0 | |
| 2.259.0 | 0 / 0 | |
| 2.258.0 | 0 / 0 | |
| 2.257.0 | 0 / 0 | |
| 2.256.0 | 0 / 0 | |
| 2.255.0 | 0 / 0 | |
| 2.254.0 | 0 / 0 | |
| 2.253.0 | 0 / 0 | |
| 2.252.0 | 0 / 0 | |
| 2.251.0 | 0 / 0 | |
| 2.250.0 | 0 / 0 | |
| 2.249.0 | 0 / 0 | |
| 2.248.0 | 0 / 0 | |
| 2.247.0 | 0 / 0 | |
| 2.246.0 | 0 / 0 | |
| 2.245.0 | 0 / 0 | |
| 2.244.0 | 0 / 0 | |
| 2.243.0 | 0 / 0 | |
| 2.242.0 | 0 / 0 | |
| 2.241.0 | 0 / 0 | |
| 2.240.0 | 0 / 0 | |
| 2.239.0 | 0 / 0 | |
| 2.238.0 | 0 / 0 | |
| 2.237.0 | 0 / 0 | |
| 2.236.0 | 0 / 0 | |
| 2.235.0 | 0 / 0 | |
| 2.234.0 | 0 / 0 | |
| 2.233.0 | 0 / 0 | |
| 2.232.0 | 0 / 0 | |
| 2.231.0 | 0 / 0 | |
| 2.230.0 | 0 / 0 | |
| 2.229.0 | 0 / 0 | |
| 2.228.0 | 0 / 0 | |
| 2.227.0 | 0 / 0 | |
| 2.226.0 | 0 / 0 | |
| 2.225.0 | 0 / 0 | |
| 2.224.0 | 0 / 0 | |
| 2.223.0 | 0 / 0 | |
| 2.222.0 | 0 / 0 | |
| 2.221.0 | 0 / 0 | |
| 2.220.0 | 0 / 0 | |
| 2.219.0 | 0 / 0 | |
| 2.218.0 | 0 / 0 | |
| 2.217.0 | 0 / 0 | |
| 2.216.0 | 0 / 0 | |
| 2.215.0 | 0 / 0 | |
| 2.214.0 | 0 / 0 | |
| 2.213.0 | 0 / 0 | |
| 2.212.0 | 0 / 0 | |
| 2.211.0 | 0 / 0 | |
| 2.210.0 | 0 / 0 | |
| 2.209.0 | 0 / 0 | |
| 2.208.0 | 0 / 0 | |
| 2.207.0 | 0 / 0 | |
| 2.206.0 | 0 / 0 | |
| 2.205.0 | 0 / 0 | |
| 2.204.0 | 0 / 0 | |
| 2.203.0 | 0 / 0 | |
| 2.202.0 | 0 / 0 | |
| 2.201.0 | 0 / 0 | |
| 2.200.0 | 0 / 0 | |
| 2.199.0 | 0 / 0 | |
| 2.198.0 | 0 / 0 | |
| 2.197.0 | 0 / 0 | |
| 2.196.0 | 0 / 0 | |
| 2.195.0 | 0 / 0 | |
| 2.194.0 | 0 / 0 | |
| 2.193.0 | 0 / 0 | |
| 2.192.0 | 0 / 0 | |
| 2.191.0 | 0 / 0 | |
| 2.190.0 | 0 / 0 | |
| 2.189.0 | 0 / 0 |
v2.288.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.287.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.286.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.231.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.230.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.229.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.228.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.227.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.226.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.225.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.224.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.223.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.222.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.221.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.220.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.219.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.218.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.217.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.216.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.215.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.214.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.213.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.212.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.211.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.210.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.209.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.208.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.207.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.206.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.205.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.204.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.203.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.202.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.201.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.200.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.199.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.198.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.197.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.196.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.195.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.194.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.193.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.192.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.191.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.190.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.189.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.