How cosm1c10/kreo-competitor-intelligence works
This repository appears to be an early product-catalog and scraper service: product records are configured for seeding into Supabase, while the sampled scraper currently exposes only a health check. The tree and excerpts do not establish a scraping-to-storage workflow, so none is shown; the Firecrawl test scripts are not treated as product runtime.
Main entry points: seed-products.js Catalog seeder · 001_initial_schema.sql Supabase database · 002_rls_policies.sql Access policies · 003_cleanup_functions.sql Cleanup functions
Components 9
Product catalog
- Product registry
config/products.json - Registry schema
config/products.schema.json - Catalog seeder
scripts/seed-products.js
Catalog persistence
- Supabase database
supabase/migrations/001_initial_schema.sql - Access policies
supabase/migrations/002_rls_policies.sql - Cleanup functions
supabase/migrations/003_cleanup_functions.sql
Scraper service
- Scraper HTTP service
services/scraper/src/index.js
Other components
- Operator
- Health-check client
Connections 6
- Operator → Catalog seeder: runs
- Catalog seeder → Product registry: reads
- Catalog seeder → Supabase database: upserts products
- Access policies → Supabase database: configures access
- Cleanup functions → Supabase database: defines cleanup
- Health-check client → Scraper HTTP service: requests health