1 check that ran failed — version behavior — so this release can’t be trusted as-is.
- Publisher
- io.github.benseverndev-oss
- Repository
- github.com/benseverndev-oss/goldencheck
- Install
- pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck, pypi:goldencheck
- Versions
- 14
- MCP revision
- 2025-11-25 · superseded
- Inspected
- 5 of 6 checks · 75%
- Scored
- 2026-09-01 · rubric 1.0.0
What we checked
Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.
Injection surface
unscannable25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.
Supply chain
pass25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
Python build script has no build-time network/exec; repository linkage verified
Credential hygiene
pass15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
Reads secrets from the environment (e.g. goldencheck/a2a/server.py) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.
Permission scope
warn15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
has both shell/exec and network egress — capable of download-and-run, though no such path was observed (goldencheck/cli/main.py: subprocess.* call; goldencheck/server.py: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (goldencheck/cli/main.py: subprocess.* call; goldencheck/config/settings.py: open(…, 'w'/'a'/'x') write-mode file access). discloses shell/exec capability: goldencheck/cli/main.py: subprocess.* call discloses broad/destructive filesystem access: 5 files (goldencheck/config/settings.py, goldencheck/config/writer.py, goldencheck/engine/history.py, +2 more) Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.
Version behavior
fail10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 3.2.0 (minor bump): new capability primitive(s) in source: fs-write, subprocess; new hardcoded outbound host/BCC destination(s): 0.0.0.0, avatars.githubusercontent.com, bad-email.org, bensevern.dev, benzsevern.github.io, example.com, github.com, raw.githubusercontent.com.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
remote endpoint present with no declared auth mode (unable to confirm authentication); manifest/source references tracking behavior — disclosure
Version history
Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v3.5.0 · current | 2026-08-16 | B | 77.5 | 5/6 · 75% | A→B in v3.5.0 |
| v3.2.0 | 2026-07-16 | A | 90 | 5/6 · 90% | B→A in v3.2.0 |
| v1.4.1 | 2026-07-02 | B | 82.5 | 5/6 · 90% | — |