@scrabble-solver/constants
Scrabble Solver 2 - Constants
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
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 2.16.5 | 0 / 0 | |
| 2.16.4 | 0 / 0 | |
| 2.16.3 | 0 / 0 | |
| 2.16.2 | 0 / 0 | |
| 2.16.1 | 0 / 0 | |
| 2.16.0 | 0 / 0 | |
| 2.15.25 | 0 / 0 | |
| 2.15.24 | 0 / 0 | |
| 2.15.23 | 0 / 0 | |
| 2.15.22 | 0 / 0 | |
| 2.15.21 | 0 / 0 | |
| 2.15.20 | 0 / 0 | |
| 2.15.19 | 0 / 0 | |
| 2.15.18 | 0 / 0 | |
| 2.15.17 | 0 / 0 | |
| 2.15.16 | 0 / 0 | |
| 2.15.15 | 0 / 0 | |
| 2.15.14 | 0 / 0 | |
| 2.15.13 | 0 / 0 | |
| 2.15.12 | 0 / 0 |
v2.16.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.