No red flags across the 5 checks that ran — clean on everything we could inspect.
- Publisher
- io.github.nickjlamb
- Repository
- github.com/nickjlamb/pubcrawl
- Install
- npm:@pharmatools/pubcrawl, npm:@pharmatools/pubcrawl, npm:@pharmatools/pubcrawl
- Versions
- 3
- Inspected
- 5 of 6 checks · 90%
- Scored
- 2026-09-03 · 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
pass25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
Scanned 110 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.
Supply chain
pass25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
repository linkage verified
Credential hygiene
pass15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.
Permission scope
pass15% of gradeDeclared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.
No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.
Version behavior
pass10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 2.0.0 (minor bump): new tool "search_pubmed" appeared; new tool "search_europepmc" appeared; new tool "get_abstract" appeared; new tool "get_full_text" appeared; new tool "find_related" appeared; new tool "format_citation" appeared; new tool "trending_papers" appeared; new tool "get_uspi" appeared; new tool "get_smpc" appeared; new tool "compare_labels" appeared; new tool "search_by_indication" appeared; new tool "resolve_drug_name" appeared; new tool "search_trials" appeared; new tool "get_trial" appeared. Low-severity drift (informational; consistent with the version bump).
Transport config
unscannable10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.
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 |
|---|---|---|---|---|---|
| v2.5.0 · current | 2026-07-30 | A | 100 | 5/6 · 90% | B→A in v2.5.0 |
| v2.0.0 | 2026-02-16 | B | 100 | 3/6 · 55% | — |