vercel/react-tweet
main · 074901dCached · audited 10 September 2026react-tweet installs, builds, and satisfies its README quickstart cleanly, but the monorepo has no automated test suite at all and its lint pipeline is broken, leaving quality and CI parity effectively unverifiable.
The core promise — install, build, embed a tweet — works and works fast, so time-to-first-value is solid. Behind that thin surface, though, there is no test suite of any kind (unit, integration, snapshot) across 110 scanned files, the CI workflow only handles releases with no test step, and running the repo's own lint script fails outright for two of five packages. Error handling throughout the API and UI layers is limited to generic thrown Errors and swallowed console.error calls with no codes…
Nine areas
Findings
Five, ranked by severity. Every one carries the command that proves it and a prompt that closes it.
pnpm run lint fails for custom-tweet-dub and next-app with 'Invalid project directory' error
Running the repository's own lint script exits 1 for two of five packages with a Next.js 'Invalid project directory' error, meaning the documented/available quality gate is broken for most of the monorepo. This blocks contributors and CI from ever running a passing lint check.
Run `pnpm run lint` from repo root; it should exit 0 (or fail only on real lint violations, not an invalid-directory error) for every workspace package.
Hard gates
A gate fires only on an observed failure. Our execution budget is 10 minutes; the standard allows 15; a gate the budget cut before it could be observed reads unverified.