[evandroribeiro94]

Description

Closes #13.

Provides comprehensive tooling adoption tracking and visualization across verified and likely HackMeridian projects:

1. Stack & Tooling Detectors (apps/api/src/hackproof/github/dependencies.py & scan.py):

   • OpenZeppelin Stellar Contracts: Detects stellar-contracts, openzeppelin-stellar-contracts, and @openzeppelin/contracts across Cargo.toml and package.json manifests.
   • Ecosystem Kits: Detects @creit.tech/stellar-wallets-kit, @stellar/freighter-api, and passkey-kit / @stellar/passkey-kit.
   • Major SDK Version Parsers: Extracts major version distributions for soroban-sdk and @stellar/stellar-sdk (e.g. v22, v21, v14, v13).
   • Frontend Frameworks: Identifies Next.js vs Vite vs Other based on dependencies.
   • AI Developer Tooling & Prompts: Scans file trees for CLAUDE.md, AGENTS.md, Cursor rules (.cursorrules, .cursor/rules), and GitHub Copilot instructions (.github/copilot-instructions.md).

2. Database & API Route (db.py, queries.py, routes.py, schemas.py):

   • Added tooling JSONB column to repos table.
   • Built GET /api/tooling returning structured categories with project counts and percentages.
   • Fully integrates with opt-out filtering to exclude hidden projects.

3. Frontend Page & Components (apps/web):

   • Built reusable DistributionBar component (apps/web/src/components/charts/distribution-bar.tsx) with animated proportional bars.
   • Built /tooling page (apps/web/src/pages/tooling.tsx, registered in App.tsx).
   • Added navigation link in site-header.tsx.

Verification

• pytest apps/api/tests/test_dependencies.py apps/api/tests/test_tooling_api.py: 11/11 passed in 8.94s
  • Fixtures for Cargo.toml, package.json, frameworks, AI files, version parsers, and API serialization all tested.
• ruff check src/ tests/: 0 errors
• pnpm build (tsc -b && vite build): Built cleanly in 3.00s (0 errors)
• pnpm oxlint: 0 errors
• pnpm prettier: All files formatted

[vercel]

Someone is attempting to deploy a commit to the Payroutes OSS Team on Vercel.

A member of the Team first needs to authorize it.