Spatial-NVR / SpatialNVR
Spatial-NVR/SpatialNVR holds a health index of 38 out of 100, placing it in the Weak band. It scores highest on AI Readiness (80/100) and lowest on Security (1/100). It was last updated 220 days ago. A single contributor accounts for most of its recent work.
Software health index
Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.
Score profile
Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.
The weighted overall 42 is calibrated to 38 on the published index scale (record calibration 2026-08-02).
Ownership
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish |
|---|---|---|---|---|---|
| Go | github.com/Spatial-NVR/SpatialNVR | v0.0.59 | - | 77 | 221 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
Development activity
How it's scored
| 3.6/36 | Push recency — last push 220 days ago |
| 2.1/36 | Commit cadence — 3/52 weeks with commits |
| 18/18 | Commit volume — 181 commits in the last year |
| 0/10 | OpenSSF Scorecard: Maintained — no data |
Inputs used
| commits_last_year | 181 |
| human_commit_share | 0.62 |
| days_since_last_push | 220 |
| active_weeks_last_year | 3 |
Release discipline
How it's scored
| 27/27 | Ships releases — 70 releases published |
| 16.2/36 | Release recency — latest release 220 days ago |
| 27/27 | Release cadence — a release every ~0.2 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 70 |
| latest_release_tag | v0.0.60-api |
| releases_from_tags | no |
| days_since_latest_release | 220 |
| mean_days_between_releases | 0.2 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
Popularity & adoption
How it's scored
| 0/60 | Stars — 0 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 0 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (MIT) |
| 18/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 0 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
Maintainer resilience (bus factor)
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0/22.5 | Commit distribution — top contributor authored 100% of commits |
| 1.4/13.5 | Contributor breadth — 1 contributors |
| 0/10 | OpenSSF Scorecard: Contributors — no data |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 1 |
| top_contributor_share | 1 |
Ownership & stewardship
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 0/25 | Owner reach — 0 followers of Spatial-NVR |
| 6.4/25 | Track record — 4 public repos, account ~0 yr old |
Inputs used
| followers | 0 |
| owner_type | Organization |
| is_verified | — |
| owner_login | Spatial-NVR |
| public_repos | 4 |
| account_age_days | 233 |
Package maintenance
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on go |
| 26/35 | Publish recency — latest publish 221 days ago |
| 20/20 | Version history — 77 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/Spatial-NVR/SpatialNVR |
| ecosystems | go |
| any_deprecated | no |
| min_days_since_publish | 221 |
Engineering Quality
Are baseline engineering and documentation practices in place?
Engineering practices
How it's scored
| 24/24 | CI workflows — 5 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — eslint.config.js |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 0/20 | OpenSSF Scorecard: CI-Tests — no data |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 0/15 | Documentation / homepage site |
| 0/10 | Repository description |
| 0/10 | Topics |
| 0/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | no |
| homepage | — |
| docs_site | — |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | no |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
Security posture
How it's scored
| 0/30 | Security policy (SECURITY.md) |
| 0/25 | Dependabot config |
| 0/25 | Dependency lockfiles — published library — lockfiles are an application concern, not expected |
| 0/20 | CodeQL workflow |
Inputs used
| source | file_signals |
| lockfiles | go.sum, package-lock.json |
| manifests | detection-service/requirements-coral.txt, detection-service/requirements-gpu.txt, detection-service/requirements-openvino.txt, detection-service/requirements.txt, e2e/package.json, go.mod, web-ui/package.json |
| has_codeql_workflow | no |
| has_security_policy | no |
| has_dependabot_config | no |
AI Readiness
How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.
Agent context & guidance
How it's scored
| 45/45 | Agent instructions — CLAUDE.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 60 of 62 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 0.968 |
| agent_instruction_files | CLAUDE.md |
| agent_instruction_max_bytes | 1,390 |
Verify loop (build / test / typecheck)
How it's scored
| 12.6/18 | One-command bootstrap — go.mod (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — eslint.config.js |
| 11/11 | Static type checking — web-ui/tsconfig.json |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 10/10 | Demonstrated agent practice — 60 of the last 100 commits agent-authored or agent-credited |
| 0/8 | Automated maintenance — no automated dependency updates observed |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — no data |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | go.sum, package-lock.json |
| has_dockerfile | yes |
| typed_language | yes |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | web-ui/tsconfig.json |
| agent_commit_share | 0.6 |
| toolchain_manifests | go.mod |
| dependency_bot_commit_share | 0 |
Code legibility for models
How it's scored
| 45/45 | Type-checkable code — Go (statically typed) |
| 54.4/55 | Manageable file sizes — 2/183 source files over 60KB |
Inputs used
| primary_language | Go |
| largest_source_bytes | 77,029 |
| source_files_sampled | 183 |
| oversized_source_files | 2 |
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — internal/proto/detection.proto |
| 0/20 | MCP server |
| 0/40 | Runnable examples |
Inputs used
| example_dirs | — |
| has_mcp_signal | no |
| api_schema_files | internal/proto/detection.proto |
| interfaces_expected_of | network-service |
Key facts
Data collection warnings
- Could not fetch npm package 'nvr-e2e-tests' from its registry
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
- OpenSSF Scorecard did not return a usable result (2026/08/17 07:33:43 Warning: PATs stored in env variables GITHUB_AUTH_TOKEN and GITHUB_TOKEN differ. Scorecard will use the former.); skipping Scorecard checks
More detail
Direct dependencies 21
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| npm | playwright | ^1.57.0 | e2e/package.json |
| Go | github.com/fsnotify/fsnotify | v1.9.0 | go.mod |
| Go | github.com/go-chi/chi/v5 | v5.2.3 | go.mod |
| Go | github.com/go-chi/cors | v1.2.2 | go.mod |
| Go | github.com/google/uuid | v1.6.0 | go.mod |
| Go | github.com/gorilla/websocket | v1.5.3 | go.mod |
| Go | github.com/mattn/go-sqlite3 | v1.14.32 | go.mod |
| Go | github.com/nats-io/nats-server/v2 | v2.10.24 | go.mod |
| Go | github.com/nats-io/nats.go | v1.38.0 | go.mod |
| Go | gopkg.in/yaml.v3 | v3.0.1 | go.mod |
| npm | @tanstack/react-query | ^5.60.0 | web-ui/package.json |
| npm | class-variance-authority | ^0.7.0 | web-ui/package.json |
| npm | clsx | ^2.1.1 | web-ui/package.json |
| npm | framer-motion | ^11.11.0 | web-ui/package.json |
| npm | hls.js | ^1.6.15 | web-ui/package.json |
| npm | lucide-react | ^0.460.0 | web-ui/package.json |
| npm | react | ^18.3.1 | web-ui/package.json |
| npm | react-dom | ^18.3.1 | web-ui/package.json |
| npm | react-router-dom | ^7.0.0 | web-ui/package.json |
| npm | tailwind-merge | ^2.5.4 | web-ui/package.json |
| npm | zustand | ^5.0.0 | web-ui/package.json |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
Raw JSON report machine-readable
Feedback
Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.
Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.
Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.31.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — Go.