superdesigndev/treg
Canonical URL: https://github.com/superdesigndev/treg · Fetched from: https://raw.githubusercontent.com/superdesigndev/treg/HEAD/README.md · Machine form: /v1/resource-scans/github-com-superdesigndev-treg-8b01562a54 · Markdown
Latest receipt: 5 of 8 checks flagged — the findings below are the record. SHA-256 of the exact bytes scanned: cd8652c7d91d361f7aa4119bddefb65cb29d1a2baba248024fd0d70c911dca8a · 33059 bytes · scanned 2026-11-03T02:46:06.484Z · scanner resource-scan-v1 · ledger entry 6103.
The rightshold on https://github.com/superdesigndev/treg — scanned 2026-11-03 · 5 of 8 checks flagged · receipt rsc_9c1123c396982818aebc532c, verify at rightshold.com/verify.
Analysis is static only: the bytes were read as text and were never executed, installed or run. Nothing was fetched from behind a login.
Checks (latest receipt)
Outbound network references — flag
The scanned bytes reference outbound network activity to these domains: api.intercom.io, api.stripe.com, docs.astral.sh, github.com, googleads.googleapis.com, llmstxt.org, skills.sh, treg.to, www.googleapis.com. Any resource that reaches the network can send data out as well as bring data in; the findings name what the bytes reference, and the reader decides whether that fits the resource's stated purpose.
Evidence: domain: api.intercom.io; domain: api.stripe.com; domain: docs.astral.sh; domain: github.com; domain: googleads.googleapis.com; domain: llmstxt.org; domain: skills.sh; domain: treg.to; domain: www.googleapis.com
Credential and environment access — flag
The scanned bytes contain credential or environment access patterns: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); credential file paths (.env, .ssh, credential stores). The receipt names the pattern kinds only; no credential value is reproduced here.
Evidence: secret-named variables (API_KEY, SECRET, TOKEN, PASSWORD and similar names); credential file paths (.env, .ssh, credential stores)
Install and postinstall hooks — pass
No install or postinstall hooks were found in the scanned bytes.
Obfuscation and encoded payloads — pass
No obfuscation or encoded-payload signs were found in the scanned bytes.
Shell-outs and download-and-execute — flag
The scanned bytes contain shell-out or download patterns: shell command tools named in the bytes (curl, wget, powershell); download-and-execute pattern (fetched content passed to an executor in the same file). Code that runs shell commands acts with the full permissions of whoever runs it.
Evidence: shell command tools named in the bytes (curl, wget, powershell); download-and-execute pattern (fetched content passed to an executor in the same file)
Permission declarations vs behavior — flag
The bytes show network, credentials behavior, and no permissions declaration was found in the scanned bytes to compare it against.
Evidence: behavior: network; behavior: credentials
Known-bad indicators — flag
The scanned bytes match these known-bad indicators from the scanner's published pattern list: pipe-to-shell: a download piped straight into a shell interpreter. Each match is a reproducible pattern match on the bytes named by the hash; re-running the published check on the same bytes reaches the same finding.
Evidence: pipe-to-shell: a download piped straight into a shell interpreter
Provenance facts (weak signals) — pass
Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: superdesigndev/treg; bytes scanned: 33059; fetched from: https://raw.githubusercontent.com/superdesigndev/treg/HEAD/README.md.
Evidence: source host: github.com; repository: superdesigndev/treg; bytes scanned: 33059; fetched from: https://raw.githubusercontent.com/superdesigndev/treg/HEAD/README.md
History
The bytes at this URL have changed across receipts: each distinct SHA-256 in the history is a distinct version of the artifact, recorded as its own receipt and never merged or overwritten.
- 2026-11-03 — 5 of 8 checks flagged · SHA-256 cd8652c7d91d361f… · 33059 bytes · scanner resource-scan-v1 · ledger entry 6103
- 2026-11-02 — 5 of 8 checks flagged · SHA-256 4c290310d1796e0a… · 32939 bytes · scanner resource-scan-v1 · ledger entry 5845
