@windyroad/tdd
TDD state machine enforcement (Red-Green-Refactor cycle)
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:zod | AI (typosquat): Scoped package @windyroad/tdd is not a typosquat of zod; the Levenshtein match is a false positive — unrelated domain, unrelated purpose, established @windyroad namespace. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 0 / 0 | |
| 0.3.1 | 0 / 0 | |
| 0.3.0 | 0 / 0 | |
| 0.2.0 | 0 / 0 | |
| 0.1.1 | 0 / 0 |
v0.5.0
1 finding[Reject — re-review on republish] (prior reject: AI (provenance): Provenance regression on a young package with no ecosystem trust is a strong unauthorized-publish signal.) This version was published without provenance, but prior versions were published via CI/CD with attestations. This is a strong signal of a potential account compromise or unauthorized publish. Multiple high-profile registry compromises have exhibited exactly this pattern.