List view
Bring public-facing documentation into alignment with the implemented package, repository layout, and maintainer operations.
No due date•3/3 issues closedPreventive checks for workflow correctness, publish-surface integrity, dependency posture, and release validation.
No due date•5/5 issues closedGitHub Actions cleanup and validation work identified during workflow log review.
No due date•2/2 issues closedConcrete fixes from the critical review of the v1 core: hook error classification, response body semantics in hooks, and response-type-aware TypeScript return typing.
No due date•14/14 issues closedExpand unit, integration, and cross-runtime coverage to match the package’s reliability and security positioning.
No due date•4/4 issues closedPackage metadata hardening, security documentation, and release/CI protections required before treating clearfetch as a security-focused package.
No due date•4/4 issues closedFoundation work for the first implementation phase of clearfetch: package scaffolding, core request pipeline, client API, errors, retries, hooks, tests, and docs.
No due date•7/7 issues closed