updated 2026-08-17 23:32 UTC

Working Activity

ccch1mneyyy/working-activity

Lively Working-line extension for pi CLI and DSH

Agent Skills TypeScript Grade D Listed MIT
21.6/100
Rank #109 of 159
Compare Working Activity

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-16 · 1d ago
Recent change
New

Is Working Activity safe? Working Activity scores 21.6/100 (Grade D), ranked #109 of 159 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 3% of recent commits are signed; last pushed 2026-08-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#107 Skillshare — 21.7 (D) → #108 Generative Media Skills — 21.7 (D) → #110 Itr Wala — 21.5 (D) → #111 Shuorenhua — 21.5 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-16
Newly Listed
First tracked at rank #109
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Working Activity View Agent Skills Report missing data
72.8
Activity sub-score · out of 100
#109
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-17 23:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-16 2026-08-17

Activity & Reach

Stars
649
Forks
231
Last Push
2026-08-16
yesterday
Commits (4 wk)
39
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
2
Rank Change
=
was #109

Analysis

HVTrust Dimensions vs Agent Skills

21.6 / 100 · 50.0% confidence

Working Activity Agent Skills average (159 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.1 / 25
2.6 below avg 2.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.5
Maintenance60% last-push freshness · 40% commit activity
18.3 / 20
3.1 above avg 15.2
AdoptionLog-scaled stars · package downloads
6.8 / 20
2.4 below avg 9.2

Activity Inputs

72.8 / 100
StarsRepository reach
16.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
20.0 / 25
CommunityFork signal
11.0 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
3%
of last 100 commits verified

Is Working Activity safe?

Public trust evidence for Working Activity is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Working Activity publish package provenance?
No published build provenance is currently detected for Working Activity. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Working Activity have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Working Activity. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Working Activity actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Working Activity use?
Working Activity ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Working Activity's commits signed?
2% of the last 100 commits to Working Activity are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Extensions
Extension based plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Working Activity?

For maintainers

HVTrust scores Working Activity from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-08-16
Newly Listed
First tracked at rank #109
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 21.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/working-activity.svg)](https://hvtracker.net/agents/working-activity)
HTML:
<a href="https://hvtracker.net/agents/working-activity"><img src="https://hvtracker.net/badge/working-activity.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON