Safety rating · all kinds

sansan0/TrendRadar

Score 31/100 — Limited public signals

Automated checks of public signals as of the date shown. Not a security audit, certification or endorsement, and not a statement about the people who maintain the project. Signals can be incomplete or out of date; each check shows its evidence and source so anyone can verify it.

Checks

• Credential and environment access — Not found (0/15): The scan flagged this check: 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.
• Known-bad indicators — Not found (0/15): The scan flagged this check: 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.
• Shell-outs and download-and-execute — Not found (0/12): The scan flagged this check: 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.
• Install and postinstall hooks — Found (12/12): The scan recorded a pass: No install or postinstall hooks were found in the scanned bytes.
• Obfuscation and encoded payloads — Found (10/10): The scan recorded a pass: No obfuscation or encoded-payload signs were found in the scanned bytes.
• Outbound network references — Not found (0/10): The scan flagged this check: The scanned bytes reference outbound network activity to these domains: api.day.app, api.slack.com, api.telegram.org, apps.apple.com, astral.sh, bark.day.app, core.telegram.org, dash.cloudflare.com, developer.work.weixin.qq.com, docs.ntfy.sh, f-droid.org, github.com, hooks.slack.com, hub.docker.com, img.shields.io, linux.do, mp.weixin.qq.com, newsnow.busiyi.world, ntfy.sh, ntfy.yourdomain.com, ocr.sandev.cc, open.feishu.cn, pages.cloudflare.com, play.google.com, sansan0.github.io, slack.com, star-history.dera.page, telegram.org, trendradar.sandev.cc, trendshift.io, weixin.qq.com, work.weixin.qq.com, www.apismart.ai, www.feishu.cn, www.rapidproxy.io, www.swiftproxy.net. 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 purp
• Permission declarations vs behavior — Not found (0/10): The scan flagged this check: The bytes show network, credentials behavior, and no permissions declaration was found in the scanned bytes to compare it against.
• Provenance facts (weak signals) — Found (6/6): The scan recorded a pass: Provenance facts, labeled weak signals — they say where the bytes sit, not what the bytes do: source host: github.com; repository: sansan0/TrendRadar; bytes scanned: 158651; fetched from: https://raw.githubusercontent.com/sansan0/TrendRadar/HEAD/README.md.