@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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 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 |
v3.27.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.