spherecast-network
mcp
Warn
Health Warn
- No license — Repository has no license file
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Pass
- Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
- Permissions — No dangerous permissions requested
Purpose
This project is a web application and dashboard for the "Spherecast Network," built for the TUM.ai Hackathon 2026. It serves as a sourcing and network visualization tool using Next.js, Python, and Supabase.
Security Assessment
The overall risk is rated as Low. The automated code scan reviewed 12 files and found no dangerous patterns, hardcoded secrets, or requests for dangerous permissions. Because it is a standard web application, it inherently makes network requests to fetch APIs (such as MapLibre and Supabase) and processes user inputs, though it utilizes Zod for input validation. It does not appear to execute arbitrary shell commands.
Quality Assessment
The repository is very new and actively maintained, with its most recent push occurring today. However, it has low community visibility (5 stars) because it was recently developed for a hackathon. A significant drawback is the complete absence of a license file, which means the software is technically under exclusive copyright and there are no formal terms granted for reuse, modification, or distribution.
Verdict
Use with caution — the codebase appears safe without hidden exploits, but the complete lack of a software license makes it legally risky to integrate into other projects.
This project is a web application and dashboard for the "Spherecast Network," built for the TUM.ai Hackathon 2026. It serves as a sourcing and network visualization tool using Next.js, Python, and Supabase.
Security Assessment
The overall risk is rated as Low. The automated code scan reviewed 12 files and found no dangerous patterns, hardcoded secrets, or requests for dangerous permissions. Because it is a standard web application, it inherently makes network requests to fetch APIs (such as MapLibre and Supabase) and processes user inputs, though it utilizes Zod for input validation. It does not appear to execute arbitrary shell commands.
Quality Assessment
The repository is very new and actively maintained, with its most recent push occurring today. However, it has low community visibility (5 stars) because it was recently developed for a hackathon. A significant drawback is the complete absence of a license file, which means the software is technically under exclusive copyright and there are no formal terms granted for reuse, modification, or distribution.
Verdict
Use with caution — the codebase appears safe without hidden exploits, but the complete lack of a software license makes it legally risky to integrate into other projects.
Spherecast Network | TUM.ai Hackathon 2026
README.md
Spherecast Network
Monorepo for the Spherecast Network sourcing and network dashboard.
| Area | Stack |
|---|---|
| Web app (repo root) | Next.js 16 (App Router) · React 19 · TypeScript (strict) · Tailwind CSS 4 · shadcn/ui (Radix) · pnpm · typically deployed on Vercel |
| Backend | Python service under backend/ (historically the optily repo, merged with history preserved). See backend/README.md for architecture, endpoints, and local run instructions. |
| Concern | Notes |
|---|---|
| UI & data | Server Components by default; use client only where needed. Validate inputs with Zod. |
| Shell & tables | Layout (Sidebar, AppTopNav), feature components under components/. |
| Network map | Deck.gl + react-map-gl / MapLibre (SupplierNetworkMap, app/api/network-map). |
| Similarity map | Plotly gl3d (plotly.js/dist/plotly-gl3d + react-plotly.js/factory), app/api/similarity-map. |
| Data | Supabase (lib/supabase*.ts, lib/queries.ts); demo or fixture data where there is no live backend yet. |
| Scope | Company filter via cookie and Server Actions (app/actions/company-scope.ts, lib/company-scope-*.ts). |
Repository layout
Frontend (Next.js) — project root:
app/
layout.tsx, page.tsx, globals.css
(app)/layout.tsx # App shell, navigation, CompanyScopeProvider
(app)/*/page.tsx # Routes: cockpit, network-map, similarity-map, suppliers, …
api/*/route.ts # JSON APIs for maps (dynamic / no-store where needed)
actions/ # Server actions (e.g. company scope)
components/
ui/ # shadcn — do not hand-edit; extend via CLI
layout/, cockpit/, network-map/, similarity-map/, sourcing/, opportunities/
lib/ # Queries, Supabase, map/plot helpers, utils (`cn`)
types/ # e.g. Plotly gl3d ambient types
**Backend** — self-contained under `backend/` (API, data, caches, Python dependencies). It is not wired into the Next.js build; run and deploy it separately until integration work is done.
## Commands (frontend)
```bash
pnpm install
cp .env.example .env.local # set values
pnpm dev # may run predev to clear stale dev locks
pnpm build && pnpm start
pnpm tsc --noEmit
Backend
See backend/README.md for the supply-chain intelligence stack (ingestion, enrichment, LLM extraction, vector search, API routes) and how to run it locally.
Conventions
Additional notes for agents and Git/PR workflow: CLAUDE.md and AGENTS.md.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found