@grammyjs/types
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
Keywords
Versions (showing 51 of 56)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 0 / 1 | |
| 3.28.0 | 0 / 1 | |
| 3.27.3 | 0 / 1 | |
| 3.27.2 | 0 / 1 | |
| 3.27.1 | 0 / 1 | |
| 3.27.0 | 0 / 1 | |
| 3.26.0 | 0 / 1 | |
| 3.25.0 | 0 / 1 | |
| 3.24.0 | 0 / 1 | |
| 3.23.0 | 0 / 1 | |
| 3.22.2 | 0 / 1 | |
| 3.22.1 | 0 / 1 | |
| 3.22.0 | 0 / 1 | |
| 3.21.0 | 0 / 1 | |
| 3.20.0 | 0 / 1 | |
| 3.19.0 | 0 / 1 | |
| 3.18.0 | 0 / 1 | |
| 3.17.0 | 0 / 1 | |
| 3.16.0 | 0 / 1 | |
| 3.15.0 | 0 / 1 | |
| 3.14.0 | 0 / 1 | |
| 3.13.0 | 0 / 1 | |
| 3.12.0 | 0 / 1 | |
| 3.11.1 | 0 / 1 | |
| 3.11.0 | 0 / 1 | |
| 3.10.0 | 0 / 1 | |
| 3.9.0 | 0 / 1 | |
| 3.8.1 | 0 / 1 | |
| 3.8.0 | 0 / 1 | |
| 3.7.0 | 0 / 1 | |
| 3.6.2 | 0 / 1 | |
| 3.6.1 | 0 / 1 | |
| 3.6.0 | 0 / 1 | |
| 3.5.2 | 0 / 1 | |
| 3.5.1 | 0 / 1 | |
| 3.5.0 | 0 / 1 | |
| 3.4.6 | 0 / 1 | |
| 3.4.5 | 0 / 1 | |
| 3.4.4 | 0 / 1 | |
| 3.4.3 | 0 / 1 | |
| 3.4.2 | 0 / 1 | |
| 3.4.1 | 0 / 1 | |
| 3.4.0 | 0 / 1 | |
| 3.3.1 | 0 / 1 | |
| 3.3.0 | 0 / 1 | |
| 3.2.2 | 0 / 1 | |
| 3.2.1 | 0 / 1 | |
| 3.2.0 | 0 / 1 | |
| 3.1.3 | 0 / 1 | |
| 3.1.2 | 0 / 1 | |
| 3.1.1 | 0 / 1 |
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.