Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

🛰️ StrixCamDB ingest — leads to verify (automated weekly)

Open
  • Is something wrong?
#259 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions, javascript
Domain
data, databases

Research direction

Start with scripts/strix-fetch.js and scripts/strix-filter.js, then inspect the strix-verify-queue artifact from the linked Actions run and the build-spec referenced by the issue. Verify candidate brands against manufacturers’ official documentation and record results in strix/verified/<brand>.json or as unverified leads. Done means validated entries are incorporated into data/rtsp-patterns.json and delivered through a human-merged release/* PR; the issue describes a large queue and does not specify a bounded batch.

Written by the indexing model from the issue text.

Description

community documentation enhancement help wanted

Automated weekly StrixCamDB lead sweep (scripts/strix-fetch.js + scripts/strix-filter.js). Last automated run: 2026-08-14 07:37 UTC — run log. Queue attached as the strix-verify-queue artifact on the run.

~5,303 candidate lead(s) after junk-filtering (~1,815 in brands not yet covered) — down from 5,744 / 1,863 after the filter was tightened (see Progress).

⚠️ These are unverified leads, not data. Next step (manual / agent fleet): confirm each against the manufacturer's own docs per the build-spec, then land via a human-merged release/* PR. Nothing here ships until a human merges it.

Reality check: the raw candidate count is dominated by scan-DB noise — device/chip/category strings the scanner couldn't attribute to a maker (other, china, ipc, dvr, h-264-network-dvr, cloud-ip-camera, …) plus typo/OEM dupes of already-covered brands. The genuinely-addressable set (real brands that publish an official RTSP scheme and aren't yet covered) is a small minority; most remaining leads are budget/app-only brands with no published path (→ status: unverified).

Progress (2026-09-10, on release/2.18.0)

Filter tightened — strix-filter.js now rejects generic/non-brand scan labels at the brand gate and aliases typo/OEM dupes (unview→uniview, alhua→dahua, air-live→airlive). Re-triage of the committed queue dropped 44 non-brand labels + merged 4 aliases → honest 1,815 new-coverage.

Verified a curated batch of 12 uncovered brands against their official docs → strix/verified/<brand>.json:

  • ✅ Sercomm — /img/media.sav (video+audio), /img/video.sav (video-only) — RC8120 User Manual App. B.
  • ✅ Fanvil — /h264/stream.live0 — Fanvil KB "integrate with Fanvil IP phones".
  • ⬜ DynaColor, Novus, Pixord, TriVision, Digitus, Neo-Coolcam, Zoneway, Aztech, Nexxt — status: unverified: app/ONVIF-only, defunct, or the maker never publishes a static RTSP path (candidates recorded under unverified_leads with reasons, so they aren't re-checked).

data/rtsp-patterns.json rebuilt → 183 brands / 120 verified / 351 templates.

Dominant language
JavaScript
Stars
267
Forks
21
Avg merge
4h 18m
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ch-bas/cctv-camera-database

All issues in ch-bas/cctv-camera-database

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.