Access probe — 2026-10-14
Scheduled access probe for scheduling rhizomatics/hq-private routines. No changes made other than this file.
Summary: GitHub API reads on rhizomatics/supernotify and the org repo list work. Security alert endpoints (Dependabot, code scanning, secret scanning) return 403. Other-org repos (SignalK/*, home-assistant/*) are refused because they are not in this session’s repo scope. Outbound HTTPS to community.home-assistant.io and api.npmjs.org is blocked by the egress proxy. GitHub Discussions pages are readable via WebFetch.
| # | Check | Command | Result | Error (first 150 chars) |
|---|---|---|---|---|
| 1 | Working dir and parent listing | pwd; ls -la /home |
OK | — (pwd = /home/user; /home contains claude, ubuntu, user. Other repos are not cloned under /home; hq is at /home/user/hq) |
| 2 | Open PRs, supernotify | gh api repos/rhizomatics/supernotify/pulls?state=open --jq length |
OK | — (0) |
| 3 | Open issues, supernotify (page 1) | gh api 'repos/rhizomatics/supernotify/issues?state=open&per_page=5' --jq length |
OK | — (5) |
| 4 | Comments on supernotify #265 | gh api repos/rhizomatics/supernotify/issues/265/comments --jq length |
OK | — (5) |
| 5 | Open Dependabot alerts | gh api 'repos/rhizomatics/supernotify/dependabot/alerts?state=open' --jq length |
FAIL | Resource not accessible by integration (HTTP 403) |
| 6 | Open code scanning alerts | gh api 'repos/rhizomatics/supernotify/code-scanning/alerts?state=open' --jq length |
FAIL | Resource not accessible by integration (HTTP 403) |
| 7 | Open secret scanning alerts | gh api 'repos/rhizomatics/supernotify/secret-scanning/alerts?state=open' --jq length |
FAIL | Access to this GitHub API path is not permitted through this proxy. (HTTP 403) |
| 8 | Security advisories in triage | gh api 'repos/rhizomatics/supernotify/security-advisories?state=triage' --jq length |
OK | — (0) |
| 9 | Failed Actions runs | gh api 'repos/rhizomatics/supernotify/actions/runs?status=failure&per_page=5' --jq .total_count |
OK | — (1024) |
| 10 | Popular referrers | gh api repos/rhizomatics/supernotify/traffic/popular/referrers --jq length |
FAIL | Resource not accessible by integration (HTTP 403) |
| 11 | Commits (page 1) | gh api 'repos/rhizomatics/supernotify/commits?per_page=3' --jq length |
OK | — (3) |
| 12 | Releases (page 1) | gh api 'repos/rhizomatics/supernotify/releases?per_page=3' --jq length |
OK | — (3) |
| 13 | Security and analysis settings | gh api repos/rhizomatics/supernotify --jq .security_and_analysis |
OK | — (command succeeded but printed no output; the field was not returned, so the settings are unknown) |
| 14 | Org repo count | gh api orgs/rhizomatics/repos --jq length |
FAIL | This GitHub API path is not available: sessions are bound to their configured repositories. Use repository-scoped endpoints (repos/{owner}/{repo}/... |
| 15 | Open PRs, SignalK/signalk-server | gh api 'repos/SignalK/signalk-server/pulls?state=open&per_page=3' --jq length |
FAIL | GitHub access to this repository is not enabled for this session. Use add_repo to request access. If add_repo answers that read |
| 16 | Releases, SignalK/signalk-server | gh api 'repos/SignalK/signalk-server/releases?per_page=3' --jq length |
FAIL | GitHub access to this repository is not enabled for this session. Use add_repo to request access. If add_repo answers that read |
| 17 | Name of home-assistant/architecture | gh api repos/home-assistant/architecture --jq .name |
FAIL | GitHub access to this repository is not enabled for this session. Use add_repo to request access. If add_repo answers that read |
| 18 | Open issues, rhizomatics/hq | gh api 'repos/rhizomatics/hq/issues?state=open' --jq length |
OK | — (2) |
| 19 | Discussion titles, supernotify | WebFetch https://github.com/rhizomatics/supernotify/discussions |
OK | — (titles visible, e.g. “Slack notifications (pinned)”, “RFC003: Pre-packaged Auto Notifiers”, “RFC0007: Quick Selectors…”, “Roadmap”, “RFC002: Simplifying transports and deliveries”. Some filter widgets showed “Sorry, something went wrong”) |
| 20 | Discussion titles, home-assistant org | WebFetch https://github.com/orgs/home-assistant/discussions |
OK | — (titles visible, e.g. “Proximity: add hysteresis”, “Request: option to ignore transient “unavailable” states”) |
| 21 | HA community search HTTP status | curl -s -o /dev/null -w '%{http_code}' 'https://community.home-assistant.io/search.json?q=supernotify' |
FAIL | exit 56, HTTP 000: agent proxy connect_rejected for community.home-assistant.io:443 (organization policy or unreachable) |
| 22 | npm downloads API HTTP status | curl -s -o /dev/null -w '%{http_code}' https://api.npmjs.org/downloads/point/last-week/@rhizomatics/signalk-bluetti-plugin |
FAIL | exit 56, HTTP 000: agent proxy connect_rejected for api.npmjs.org:443 (organization policy or unreachable) |
Notes for scheduling
Section titled “Notes for scheduling”- Routines that need security alerts (Dependabot, code scanning, secret scanning) or traffic data cannot run from this session as configured. The
security-escalationskill’s source data is blocked. - Cross-org reads (
SignalK/*,home-assistant/*) needadd_repofor each repo, or they will fail. - Discussion reads work through WebFetch, not the API. Titles only; nothing deeper was checked.
- Community forum search and npm download stats are blocked by proxy policy. No workaround was attempted, as instructed.