@webstudio-is/fonts
Fonts utils
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established monorepo utility package; sparse README and no keywords are expected for internal tooling. | ai |
Versions (showing 100 of 237)
| Version | Deps | Published |
|---|---|---|
| 0.282.1 | 0 / 3 | |
| 0.282.0 | 0 / 3 | |
| 0.281.0 | 0 / 3 | |
| 0.280.1 | 0 / 3 | |
| 0.280.0 | 0 / 3 | |
| 0.279.0 | 0 / 3 | |
| 0.278.0 | 0 / 3 | |
| 0.277.0 | 0 / 3 | |
| 0.276.1 | 0 / 3 | |
| 0.276.0 | 0 / 3 | |
| 0.275.0 | 0 / 3 | |
| 0.274.5 | 0 / 3 | |
| 0.274.4 | 0 / 3 | |
| 0.274.3 | 0 / 3 | |
| 0.274.2 | 0 / 3 | |
| 0.274.1 | 0 / 3 | |
| 0.274.0 | 0 / 3 | |
| 0.273.0 | 0 / 3 | |
| 0.272.0 | 0 / 3 | |
| 0.271.0 | 0 / 3 | |
| 0.270.0 | 0 / 3 | |
| 0.269.0 | 0 / 3 | |
| 0.268.0 | 0 / 3 | |
| 0.267.0 | 0 / 3 | |
| 0.266.0 | 0 / 3 | |
| 0.265.0 | 0 / 3 | |
| 0.264.0 | 0 / 3 | |
| 0.263.0 | 0 / 3 | |
| 0.262.1 | 0 / 3 | |
| 0.262.0 | 0 / 3 | |
| 0.261.1 | 0 / 3 | |
| 0.261.0 | 0 / 3 | |
| 0.260.2 | 0 / 3 | |
| 0.259.0 | 0 / 3 | |
| 0.258.0 | 0 / 3 | |
| 0.257.0 | 0 / 3 | |
| 0.255.0 | 0 / 3 | |
| 0.254.0 | 0 / 3 | |
| 0.253.0 | 0 / 3 | |
| 0.252.2 | 0 / 3 | |
| 0.252.1 | 0 / 3 | |
| 0.238.0 | 0 / 3 | |
| 0.237.0 | 0 / 3 | |
| 0.236.0 | 0 / 3 | |
| 0.235.0 | 0 / 3 | |
| 0.234.0 | 0 / 3 | |
| 0.233.0 | 0 / 3 | |
| 0.232.0 | 0 / 3 | |
| 0.231.0 | 0 / 3 | |
| 0.230.0 | 0 / 3 | |
| 0.229.0 | 0 / 3 | |
| 0.228.0 | 0 / 3 | |
| 0.227.0 | 0 / 3 | |
| 0.226.0 | 0 / 3 | |
| 0.225.0 | 0 / 3 | |
| 0.224.0 | 0 / 3 | |
| 0.223.0 | 0 / 3 | |
| 0.222.0 | 0 / 3 | |
| 0.221.0 | 0 / 3 | |
| 0.220.0 | 0 / 3 | |
| 0.219.0 | 0 / 3 | |
| 0.218.0 | 0 / 3 | |
| 0.217.0 | 0 / 3 | |
| 0.216.0 | 0 / 3 | |
| 0.215.0 | 0 / 3 | |
| 0.214.0 | 0 / 3 | |
| 0.213.0 | 0 / 3 | |
| 0.212.0 | 0 / 3 | |
| 0.211.0 | 0 / 3 | |
| 0.210.0 | 0 / 3 | |
| 0.209.0 | 0 / 3 | |
| 0.208.0 | 0 / 3 | |
| 0.207.0 | 0 / 3 | |
| 0.206.0 | 0 / 3 | |
| 0.205.0 | 0 / 3 | |
| 0.204.0 | 0 / 3 | |
| 0.203.0 | 0 / 3 | |
| 0.202.0 | 0 / 3 | |
| 0.201.0 | 0 / 3 | |
| 0.200.0 | 0 / 3 | |
| 0.199.0 | 0 / 3 | |
| 0.198.0 | 0 / 3 | |
| 0.197.0 | 0 / 3 | |
| 0.196.0 | 0 / 3 | |
| 0.195.0 | 0 / 3 | |
| 0.194.0 | 0 / 3 | |
| 0.193.0 | 0 / 3 | |
| 0.192.0 | 0 / 3 | |
| 0.191.5 | 0 / 3 | |
| 0.191.4 | 0 / 3 | |
| 0.191.0 | 0 / 3 | |
| 0.189.0 | 0 / 5 | |
| 0.185.0 | 0 / 5 | |
| 0.182.0 | 0 / 5 | |
| 0.181.0 | 0 / 5 | |
| 0.179.0 | 0 / 5 | |
| 0.175.0 | 0 / 5 | |
| 0.174.0 | 0 / 5 | |
| 0.173.0 | 0 / 5 | |
| 0.168.0 | 0 / 5 |
v0.282.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.282.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.281.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.280.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.280.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.279.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.278.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.277.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.276.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.276.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.275.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.274.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.218.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.217.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.216.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.215.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.214.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.213.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.212.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.211.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.210.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.209.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.208.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.207.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.206.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.205.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.204.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.203.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.202.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.201.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.200.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.199.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.198.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.197.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.196.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.195.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.194.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.193.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.192.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.191.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.191.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.191.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.189.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.185.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.182.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.181.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.179.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.175.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.174.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.173.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.168.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.