io.github.starloghq/starlog
NPM · STARLOGHQ
Vet a package (CVEs, license, maintenance) before your AI agent uses it, plus capability discovery.
Available components
Last scanned (1 hour ago)
Scores higher than 72% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security74
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- Declares code that runs automatically (postinstall) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
- 33 of 102 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to starloghq/index). View diagnostics → Pass
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 101 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 618 tokens (~206/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 −3
- Stability: pass → 0.80 functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −1
- Stability: pass → 0.93 functional
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 +1
- Stability: 0.97 → pass security
- 22 Oct 26 −1
- Stability: pass → 0.97 functional
- 16 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/starloghq@0.9.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | starloghq/index |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/starloghq/index/.github/workflows/publish.yml@refs/tags/v0.9.0 |
| Rekor log index | 2257217856 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0da62a7a12c3939694d7d9ce4383e37051c4519b8f599c916a69c6439bd1168300bb18ef3863e2dbeeff4c207004dd334f701ab204a764dc9a5bff8c2 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | Not reviewed | node postinstall.mjs |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 102 packages
| Packages resolved | 102 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
starlog_advise ~215
When you detect DIY or repeated capability code (auth, caching, jobs, etc.), call this BEFORE building more custom code or extracting a reusable package. It tracks patterns, searches for safe alternatives, and advises MIGRATE to a known library when one exists (e.g. Clerk/Auth0/Supabase over DIY auth) or PACKAGEIZE only when no safe corpus alternative exists. Prefer migration over packageizing commodity capabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Capability category filter. Known: authentication, feature-flags, caching, realtime, background-jobs, email, orm-database |
| context | string | – | Project context for search ranking, e.g. "Next.js B2B SaaS" |
| force | boolean | – | Advise migration/packageize even when recurrence is below threshold |
| observation | string | – | What you observed, e.g. "hand-rolled JWT auth" or "third project with custom session middleware" |
| project_root | string | – | Absolute path to scan for DIY patterns (defaults to cwd) |
No output schema declared.
No examples provided.
starlog_facts ~115
Look up authoritative facts about a software package: known vulnerabilities/CVEs and supply-chain incidents, SPDX license and license risk, maintenance status (active/deprecated/abandoned/compromised), and what the package can do (effect surface). Use it to vet a package before recommending it.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional project context for relevance, e.g. "Next.js SaaS, needs SSO" |
| package | string | yes | The package name to look up, e.g. "ua-parser-js" |
No output schema declared.
No examples provided.
starlog_search ~288
Discover candidate packages for a capability: surfaces options for a need (org-sanctioned/private ones first when configured), with integration effort, best-for and skip-when notes. This is discovery — it surfaces what exists; to vet a specific named package (CVEs, license, maintenance), call starlog_facts. Use after you have a capability/need and want candidate package names.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter to a category. Known categories: authentication, feature-flags, caching, realtime, background-jobs, email, orm-database. Any other string is accepted for dynamic categories (parity with the CL… |
| context | string | – | Project context to unlock DIY-vs-buy analysis, e.g. "B2B SaaS on Next.js + Postgres, small team, needs SSO soon" |
| diversity_lambda | number | – | Diversity-relevance tradeoff (0=max diversity, 1=pure relevance). Omit to use the default diversity rerank (0.5). |
| query | string | yes | What you need, e.g. "auth for Next.js SaaS" or "background job queue for Node.js" |
| stack | string | – | Filter by stack affinity, e.g. "next.js", "python", "react" |
| top_k | integer | – | Max results to return, 1-50 (default 5) |
No output schema declared.
No examples provided.
How do I install the io.github.starloghq/starlog MCP server?
io.github.starloghq/starlog runs locally as an npm package, launched with npx -y starloghq mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · starloghq
claude mcp add starloghq-starlog -- npx -y starloghq mcp
What is the io.github.starloghq/starlog MCP server?
io.github.starloghq/starlog is an MCP server listed in the public MCP registry as io.github.starloghq/starlog. Vet a package (CVEs, license, maintenance) before your AI agent uses it, plus capability discovery. This page covers its npm package (starloghq).
Is the io.github.starloghq/starlog MCP server safe to use?
io.github.starloghq/starlog scores 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.starloghq/starlog MCP server expose?
io.github.starloghq/starlog exposes 3 tools: starlog_search, starlog_facts, starlog_advise. Their descriptions and schemas cost roughly 618 tokens of context every time the server is loaded.
Is the io.github.starloghq/starlog MCP server still maintained?
io.github.starloghq/starlog is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.starloghq/starlog MCP server under?
io.github.starloghq/starlog declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.
What did VerifyMCP test on the io.github.starloghq/starlog MCP server?
VerifyMCP ran 16 checks on io.github.starloghq/starlog, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.