agentleFS
lgtm-hqlgtm-hq/ai-skills/skills/scorecard/SKILL.md

scorecard

Skill1 starsChanged 11 days agoMITView on GitHub

Audit the OpenSSF Scorecard rating for py-lintro. Use when asked to check the scorecard, understand the rating, or find what's missing. Specific to github.com/lgtm-hq/py-lintro.

  • Installs packages

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the following to get the latest scorecard results:

    line 13
  2. Distinctive:

    If the audit reveals new findings, outdated information, or checks that have been resolved, update the baseline table in this skill file:

    line 107
  3. Distinctive:

    Update the following sections:

    line 114

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenSSF Scorecard Audit — py-lintro

Audit the OpenSSF Scorecard rating for github.com/lgtm-hq/py-lintro and identify what's dragging the score down.

Step 1: Fetch Current Score

Run the following to get the latest scorecard results:

# Get the latest scorecard JSON from the API
curl -s "https://api.securityscorecards.dev/projects/github.com/lgtm-hq/py-lintro" | python3 -m json.tool

Also check the scorecard viewer.

Step 2: Evaluate Each Check

Compare the live results against the baseline findings below. For each check, determine whether the score has improved, regressed, or stayed the same.

Baseline Findings (2026-02-20, score 5.8/10)

CheckScoreRoot Cause
Code-Review0/10Single maintainer — PRs by TurboCoder13 have no distinct human reviewer. CodeRabbit (AI bot) reviews don't count.
Token-Permissions0/10Workflows escalate to write permissions at the job level (packages: write, pull-requests: write, contents: write). Scorecard wants minimal top-level permissions on every workflow file.
Signed-Releases0/10PyPI attestations and Docker provenance exist but scorecard expects Sigstore signatures or actions/attest-build-provenance on GitHub Release artifacts themselves.
Pinned-Dependencies-1 (error)FROM ${TOOLS_IMAGE} ARG indirection in Dockerfile causes a scorecard parsing error. The image IS pinned by digest — this is a known scorecard limitation. Do not "fix" this — the parameterization is load-bearing (used by CI, docker-compose, Makefile, scripts for PR testing with swappable tools images). Also: apt-get install on line 48 lacks version pins.
Fuzzing0/10No OSS-Fuzz or ClusterFuzzLite integration.
CI-Tests5/10Tests detected on only ~57% of merged PRs. Bot/release PRs (from github-actions[bot]) skip full test flow, skewing the metric.
Security-Policy4/10SECURITY.md uses a personal email instead of GitHub's private vulnerability reporting.
Contributors3/10Single human contributor. Inherent to the project — cannot easily change.
CII-Best-Practices2/10OpenSSF Best Practices badge was "InProgress". User reported 99% complete as of 2026-02-20 — scorecard may lag.
Vulnerabilities7/10Open Dependabot alerts (11 at baseline).
SAST8/10CodeQL configured but may not cover all commit paths.
Branch-Protection6/10Allstar configured but requireStatusChecks is empty and requireCodeOwnerReviews is false.
Dependency-Update-Tool10/10Renovate configured and active.
Maintained10/10Active development.
Dangerous-Workflow10/10No dangerous patterns.
Binary-Artifacts10/10Clean.
Packaging10/10OIDC trusted publishing to PyPI.
License10/10MIT.

Known Non-Issues (Do Not Recommend Fixing)

  • Pinned-Dependencies / Dockerfile ARG: The FROM ${TOOLS_IMAGE} pattern is intentional and used across CI pipelines, docker-compose, Makefile, and scripts for build-time image swapping. The image is pinned by digest. Scorecard cannot parse ARG indirection — this is their bug, not ours.
  • Contributors: Single-maintainer project. Score will naturally improve if more contributors join.
  • Code-Review: Inherently limited by single-maintainer status. Would need a second trusted reviewer.

GitHub Repo Settings to Check

# Check security settings
gh api repos/lgtm-hq/py-lintro --jq '.security_and_analysis'

At baseline, these were disabled (not scored by scorecard but still worth tracking):

  • secret_scanning
  • secret_scanning_push_protection
  • dependabot_security_updates

Step 3: Report

Present findings in this format:

## OpenSSF Scorecard Audit — py-lintro

**Current Score:** X.X/10
**Previous Score:** 5.8/10 (2026-02-20)
**Trend:** Improved / Regressed / Unchanged

### Check-by-Check Comparison

| Check | Baseline | Current | Delta | Notes |
| ----- | -------- | ------- | ----- | ----- |
| ...   | ...      | ...     | ...   | ...   |

### What's Still Missing

1. [check] — [why it's still low and what would fix it]

### What Improved

1. [check] — [what changed]

### Recommended Next Actions (prioritized by score impact)

1. [action]

Step 4: Update This Skill

If the audit reveals new findings, outdated information, or checks that have been resolved, update the baseline table in this skill file:

Edit skills/scorecard/SKILL.md

Update the following sections:

  • Baseline Findings table — update scores, root causes, and the date
  • Known Non-Issues — add or remove entries as appropriate
  • GitHub Repo Settings — update if settings have changed

This keeps the skill accurate for future invocations.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.