An open compatibility testing network: does this library API actually run on your version, OS and runtime? Real build evidence, verified samples, and the environment each result came from.
- capability exposure inferred + 10
- tool safety inferred + 12
- trust mitigators mixed − 11
inferred mixed
The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.
grade last moved 1w ago · see ecosystem CVEs →
- A · 0 → A · 11
- A · 6 → A · 0
No known CVEs for this server.
- high dangerous code
committed secret: GitHub token · obfuscated payload: dynamic require()/import()
analyzed commit c1bc620 · analyzer v33 · 11h ago
danger signals1
- committed secret GitHub token r2cuerdame-CodeSampleX-c1bc620/internal/samples/credential_test.go :19
ghp_AA…(40 chars, redacted)
[](https://mcpobservatory.com/servers/github:r2cuerdame/CodeSampleX/security) Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of r2cuerdame.