Security Scan (SIAX Cloud) / security (push) Successful in 18s
CI (SIAX Cloud) / security (push) Successful in 21s
CI (SIAX Cloud) / quality (push) Successful in 42s
CI (SIAX Cloud) / security (pull_request) Successful in 20s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 16s
CI (SIAX Cloud) / quality (pull_request) Successful in 41s
13 compiled .pyc files under services/{api,scrapers}/**/__pycache__/ and 50
scraped brreg.no JSON pages under services/scrapers/output/ were committed to
git despite __pycache__/*.pyc already being covered by .gitignore -- they
predate that rule and git does not retroactively drop already-tracked files
that start matching an ignore pattern.
Neither set is referenced by any source, test, or doc as a fixture (verified
via repo-wide grep); both are pure runtime artifacts regenerated on demand.
Untrack them with git rm --cached, delete the local copies, and add
services/scrapers/output/ to .gitignore so scraper runs stop reintroducing
this. No source or test file touched; pnpm test still 156 passed / 1 honestly
skipped (realinfra ST0RE check) after the change.
Matches docs/compliance/BACKLOG.md P4-4, explicitly flagged as hygiene doable
without a product decision. Picks up unfinished work from an earlier,
never-merged branch of the same name.
0pt Scraper → b0ts
Scraper code has moved to the b0ts repo: https://git.siax.io/admin/b0ts
Quick start
git clone https://git.siax.io/admin/b0ts.git
cd b0ts
python -m src.main
API
b0ts runs on port 4115:
POST /pipeline/start— Start continuous scrapingGET /pipeline/status— Check progressGET /analytics/quality— Data quality metrics
MCP
MCP tools available at schemas/mcp/b0ts.mcp.json.
Deployment
# On SIAX Cloud Server 2
ssh -i ~/.ssh/id_ed25519_siax root@188.40.230.69
cd /opt/b0ts && python3 -m src.main