@gitlab/svgs
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 63 of 63)
| Version | Deps | Published |
|---|---|---|
| 3.163.0 | 0 / 13 | |
| 3.162.1 | 0 / 13 | |
| 3.162.0 | 0 / 13 | |
| 3.161.0 | 0 / 13 | |
| 3.160.0 | 0 / 13 | |
| 3.159.0 | 0 / 13 | |
| 3.158.0 | 0 / 13 | |
| 3.157.0 | 0 / 13 | |
| 3.156.0 | 0 / 13 | |
| 3.155.0 | 0 / 13 | |
| 3.154.0 | 0 / 13 | |
| 3.153.0 | 0 / 13 | |
| 3.152.0 | 0 / 13 | |
| 3.149.0 | 0 / 18 | |
| 3.148.0 | 0 / 18 | |
| 3.147.0 | 0 / 18 | |
| 3.146.0 | 0 / 18 | |
| 3.145.0 | 0 / 18 | |
| 3.144.0 | 0 / 18 | |
| 3.143.0 | 0 / 18 | |
| 3.142.0 | 0 / 18 | |
| 3.141.0 | 0 / 18 | |
| 3.140.0 | 0 / 18 | |
| 3.139.0 | 0 / 18 | |
| 3.138.0 | 0 / 18 | |
| 3.137.0 | 0 / 18 | |
| 3.136.0 | 0 / 18 | |
| 3.135.0 | 0 / 18 | |
| 3.134.0 | 0 / 18 | |
| 3.133.0 | 0 / 18 | |
| 3.132.0 | 0 / 18 | |
| 3.131.0 | 0 / 18 | |
| 3.130.0 | 0 / 18 | |
| 3.129.0 | 0 / 18 | |
| 3.128.0 | 0 / 18 | |
| 3.127.2 | 0 / 18 | |
| 3.127.1 | 0 / 18 | |
| 3.127.0 | 5 / 13 | |
| 3.126.0 | 0 / 13 | |
| 3.125.0 | 0 / 13 | |
| 3.124.0 | 0 / 13 | |
| 3.123.0 | 0 / 13 | |
| 3.122.0 | 0 / 13 | |
| 3.121.0 | 0 / 13 | |
| 3.120.0 | 0 / 13 | |
| 3.119.0 | 0 / 13 | |
| 3.118.0 | 0 / 13 | |
| 3.117.0 | 0 / 13 | |
| 3.116.0 | 0 / 13 | |
| 3.115.0 | 0 / 13 | |
| 3.114.0 | 0 / 13 | |
| 3.113.0 | 0 / 13 | |
| 3.112.0 | 0 / 13 | |
| 3.111.0 | 0 / 13 | |
| 3.110.0 | 0 / 13 | |
| 3.109.0 | 0 / 13 | |
| 3.108.0 | 0 / 13 | |
| 3.107.0 | 0 / 13 | |
| 3.106.0 | 0 / 13 | |
| 3.105.0 | 0 / 13 | |
| 3.104.0 | 0 / 13 | |
| 3.103.0 | 0 / 13 | |
| 3.102.0 | 0 / 13 |
v3.134.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.133.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.132.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.131.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.130.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.129.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.128.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.127.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.127.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.127.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.126.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.125.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.124.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.123.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.122.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.121.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.120.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.119.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.118.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.117.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.116.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.115.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.114.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.113.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.112.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.111.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.110.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.109.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.108.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.107.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.106.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.105.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.104.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.103.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.102.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.