@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, so a manually published version cannot be tied back to a reviewed commit.
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 18 of 118)
| Version | Deps | Published |
|---|---|---|
| 2.4.4 | 3 / 4 | |
| 2.4.3 | 3 / 4 | |
| 2.4.2 | 3 / 4 | |
| 2.4.1 | 3 / 4 | |
| 2.4.0 | 3 / 4 | |
| 2.3.3 | 3 / 3 | |
| 2.3.2 | 3 / 3 | |
| 2.3.1 | 3 / 3 | |
| 2.3.0 | 3 / 3 | |
| 2.2.2 | 3 / 6 | |
| 2.2.1 | 3 / 6 | |
| 2.2.0 | 3 / 6 | |
| 2.1.0 | 3 / 6 | |
| 2.0.4 | 3 / 6 | |
| 2.0.3 | 3 / 6 | |
| 2.0.2 | 3 / 6 | |
| 2.0.1 | 3 / 6 | |
| 2.0.0 | 3 / 6 |
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.