@scrabble-solver/solver
Scrabble Solver 2 - Solver
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
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 package; sparse README/keywords are a style choice, not spam. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo with consistent authorship and no material changes; dormancy pattern fits sporadic release cadence, not takeover. | ai | |
| typosquat | typosquat.levenshtein:semver | AI (typosquat): Scoped monorepo package; name similarity to semver is coincidental, not a typosquat. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.16.4 | 2 / 3 | |
| 2.16.3 | 2 / 3 | |
| 2.16.2 | 2 / 3 | |
| 2.16.1 | 2 / 3 | |
| 2.16.0 | 2 / 3 | |
| 2.15.25 | 2 / 3 | |
| 2.15.24 | 2 / 3 | |
| 2.15.23 | 2 / 3 | |
| 2.15.22 | 2 / 3 | |
| 2.15.20 | 2 / 3 | |
| 2.15.19 | 2 / 3 | |
| 2.15.18 | 2 / 3 | |
| 2.15.17 | 2 / 3 | |
| 2.15.16 | 2 / 3 | |
| 2.15.15 | 2 / 3 |
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.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.22
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.