basellm / llm-metadata
A lightweight interface for accessing and integrating LLM metadata, enabling applications to seamlessly discover, query, and integrate large language model information.
AI Architecture Analysis
This repository is indexed by RepoMind. By analyzing basellm/llm-metadata in our AI interface, you can instantly generate complete architecture diagrams, visualize control flows, and perform automated security audits across the entire codebase.
Our Agentic Context Augmented Generation (Agentic CAG) engine loads full source files into context on-demand, avoiding the fragmentation of traditional RAG systems. Ask questions about the architecture, dependencies, or specific features to see it in action.
Embed this Badge
Showcase RepoMind's analysis directly in your repository's README.
Repository Overview (README excerpt)
Crawler viewLLM Metadata > A lightweight static API for discovering and integrating LLM metadata. Live: > GitHub Pages · Cloudflare Pages English | 中文文档 | 日本語 High-throughput friendly, static-by-default interface: rebuild on change; serve static JSON via GitHub Pages. Sources: models.dev/api.json + basellm community contributions. Quick Start Requirement: Node.js 18+ (with native ). Outputs: Scripts: • — Compile TypeScript and build API (no-op if nothing changes) • — Force rebuild all files • — Dry-run for change detection (CI use) • — Remove and • — Compile TypeScript only • — Watch mode compilation Internationalization (Docs & API) Docs i18n is driven by and with mkdocs-static-i18n; API i18n is driven by and overrides in . Folder & config Add a language (example: ) • Add to : • Create (copy from and translate keys) • Create (translate capability labels and optional default description template) • Add (landing) and an empty (will be generated) • Optional: in add nav_translations for • Build: API i18n details • Capability labels come from and are applied to: • explicit • boolean capabilities: tools/files/reasoning/temperature/open_weights • modalities-derived tags: vision/audio • Localized API datasets are written to: • - , • per-provider/model files under • NewAPI payloads: • English (stable): • Localized: • Default description template (fallback to English): • → , placeholders: , • If a model's description equals the English default, localized builds replace it with the locale template Docs i18n (mkdocs) • Strings from ; missing keys fall back to • Build docs pages automatically on • Preview docs: then Update Modes • Manual: edit and push to main; CI builds and publishes • Automatic: scheduled fetch; incremental updates for models allowed by policy GitHub Actions triggers: • to , , etc. • manual run • every 6 hours Auto-update Policy Config: (default ). Example: If a model sets , automatic builds will not overwrite its existing static file (first build still generates it). Overrides (directory-based) Use a directory-based layout. Put small JSON fragments under the following paths and they will be deep-merged during build: Examples Provider icon override ( ): Model override ( ): Notes • Deep-merge applies; unspecified fields are preserved. • Model override allowlist (sanitization): , , , , , , , , , , , , , . • Build reads overrides from .