Repository navigation
Spawn v1.1.0
Spawn v1.1.0 — spawn inspect
Spawn can now read a repository, not just create one. Point it at any local project and get a deterministic, evidence-backed summary of what it contains.
spawn inspect # inspect the current directory
spawn inspect ./my-app # inspect a path
spawn inspect . --json # full machine-readable report on stdoutWhat spawn inspect does
- Read-only and static. It never runs project code, installs dependencies, makes network calls, or needs an LLM, and it writes nothing to the target.
- Evidence-backed. Every finding carries repo-relative evidence and one of five states:
detected,inferred,not_detected,unknown,not_checked. A dependency declaration alone is reported as inferred, not detected. - Deterministic. The same repository gives the same report, with stable ordering and no machine-specific absolute paths.
- Partial results. Unreadable or malformed files produce diagnostics and a
partialstatus instead of aborting the run.
What it detects
- Languages and frameworks: 25 languages; React, Next.js, Vue, Nuxt, Angular, Svelte, Express, FastAPI, Flask, Django, Starlette, Pydantic, Laravel.
- Dependencies and package managers: direct dependencies from
pyproject.toml,requirements*.txtandpackage.json; uv, poetry, pipenv, pip, npm, yarn, pnpm, bun. - Tooling and layout: linters, formatters, test runners, git, CI systems, Docker/Compose, database drivers, tests directory,
srclayout, and Spawn-generated projects.
Other changes
spawn --versionprints the same line asspawn version.spawn inspect --verboseshows more detail in the human report.- A documented JSON report contract (schema
1.0) withvalidate_report,to_jsonandfrom_jsoninspawn.inspection. - New exit code 7 for an invalid path or failed inspection. In
--jsonmode errors go to stderr and stdout stays empty. - Release smoke test now runs
spawn inspect . --jsonon a generated project and verifies it is unchanged. create,doctorandversionbehave exactly as before.
Known limitations
- Framework imports are matched with regular expressions. Import-like text in comments or strings can produce false positives (for example, scaffolding tools that embed sample code), and multi-line or destructured imports are missed.
- Directories named
build,dist,env,venv,target,vendor,coverageand similar are skipped at any depth. - CI, container and pre-commit detection is by file presence only; YAML is not parsed.
- Databases are inferred from driver packages only.
Pipfile,setup.py,Cargo.toml,go.mod,Gemfile,composer.json,pom.xmland Gradle files produce no dependency findings. Rails is not detected.- A pip and an npm package with the same name share one finding.
- On POSIX, filenames that aren't valid UTF-8 can break
to_jsonfor library callers (the CLI still works). A fix is planned. summary.nameis the directory name, andprimary_frameworkmay be inferred.
Upgrade
pip install -U spawnio # or: uv tool upgrade spawnioFull changelog: see docs/changelog.md