star-trajectory — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited star-trajectory (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
This skill classifies a GitHub repository's star-growth trajectory and projects a target/deadline outcome. It wraps classify.py, a single-file, zero-dependency, anonymous-API tool (no token, no file writes).
Trigger when the user asks anything like:
owner/repo still taking off, or has it plateaued?"classify.py lives at the repository root (one directory above this skill). Run:
python3 /path/to/star-trajectory/classify.py --repo <owner>/<name> --jsonapi.github.com.--target-stars N, --deadline-hours H, --prior "v1,v2" (pastvelocity readings to tell an oscillation trough from a terminal stall).
Key fields:
phase (1–4) + phase_label: launch / accel / trajectory (sustain) / maturity.projection.lean: HIT_lean / BORDERLINE / MISS_lean / LOW_CONFIDENCE.Always cite projection.uncertainty_note — direction is robust, magnitude is noisy (±~30%).
driver_vs_burst: whether velocity is sustained by active development or is adecaying burst.
discovery_onset: if a repo sat dormant then "launched", the deadline clock isre-anchored to launch, not creation.
metrics: stars, age, v_avg, v_recent, accel_ratio.Give a short, plain-language read, then the reason:
Likely yes (HIT_lean). It's in an accel phase — the most recent stars are arriving ~1.6× faster than its lifetime average, and there was a push an hour ago. Projected ~417★ by the 48h mark. (Direction is reliable; the exact number is noisy.)
Always state it's a heuristic projection, not a guarantee. If LOW_CONFIDENCE, say why (e.g. too few recent dated stars, or a one-off sharing spike).
A projected HIT built on purchased stars is meaningless. If the growth looks suspicious, also run the sibling tool fake-star-audit to check whether the stars are real.
rate_limited: the anonymous 60/h budget is spent; retry within an hour.not_found: repo is private or doesn't exist.This skill only analyses public repositories using public data.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.