user-activity — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited user-activity (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.
Retrieve a GitHub user's profile information and their contribution history (commits, PRs, issues, reviews).
usernameread:user scope (GraphQL API)search_user to get bio, organisation membership, pinned repos, and follower countsget_user_activities to get a detailed breakdown of their activity, optionally filtered by org, repo, or date rangesearch_user| Parameter | Type | Description |
|---|---|---|
username | str | GitHub username to look up |
Returns: UserSearchResult — login, name, bio, company, location, public repos count, followers/following, organisation memberships, pinned repositories.
get_user_activities| Parameter | Type | Default | Description |
|---|---|---|---|
username | str | — | GitHub username |
org | str | "" | Filter by organisation name (optional) |
repo | str | "" | Filter by repository name (optional) |
since | str | "" | Start date in ISO 8601 format: YYYY-MM-DD |
until | str | "" | End date in ISO 8601 format: YYYY-MM-DD |
max_results | int | 50 | Maximum number of contribution entries to return |
Returns: UserActivityResult — lists of commits, pull requests, issues, PR reviews, and the user's repos with current star counts.
| Type | Fields |
|---|---|
| Commits | commitCount, url, occurredAt |
| Pull Requests | PR title, state, URL, creation date |
| Issues | Issue title, state, URL, creation date |
| PR Reviews | Review state (APPROVED, CHANGES_REQUESTED, COMMENTED), PR URL |
| Repo Stars | repo, owner, url, description, star_count |
Use get_repo_stars_since — not get_user_activities. It paginates the GitHub stargazers REST endpoint (which carries starred_at timestamps) from the most recent page backwards to count stars received within the window.
get_repo_stars_since(username="saidsef", since="2024-04-01", top_n=5)Returns repos sorted by new_stars (stars received since since) descending, with total_stars for context. since defaults to 30 days ago if omitted.
repo_stars in get_user_activities returns each repo's current total star count, not stars gained within since/until. Use get_repo_stars_since instead when the question is about a time window.
YYYY-MM-DD (e.g. 2024-01-01) or full ISO 8601 (2024-01-01T00:00:00Z)since becomes T00:00:00Z, until becomes T23:59:59Zsince is inclusive (contributions on or after this date)until is inclusive (contributions on or before this date)max_resultsrepo_starsget_repo_stars_since| Parameter | Type | Default | Description |
|---|---|---|---|
username | str | — | GitHub username |
since | str | 30 days ago | Start date: YYYY-MM-DD or ISO 8601 |
top_n | int | 5 | Number of top repos to return |
max_repos | int | 20 | Max repos to check (one REST call per repo) |
Returns: RepoStarsSinceResult — repos sorted by new_stars desc, each with repo, owner, url, description, new_stars, total_stars.
search_user first — it confirms the user exists and provides context before fetching activityorg and repo filters together to scope activity to a specific projectmax_results conservatively (50–100) for broad date ranges to avoid large payloadsAPPROVED means the user approved that PR; CHANGES_REQUESTED means they blocked it~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.