Who it is for
No explicit purpose, audience or use case was extracted from the inspected README.
Automated source and domain checks for oomol-lab/open-connector.
Metal Mantra scanned this public repository on its own initiative; the maintainer did not submit it. Maintainers: scan the repository yourself to take this report over, or contact us.
Inspect GitHub sourceVotes show community interest, not safety. They never change this score.
Runtime safety, real-world agent capability, fitness for your use case or independent certification.
Structured, cited information from the scanned archive. Repository-authored claims are labeled and never treated as verified capabilities.
No explicit purpose, audience or use case was extracted from the inspected README.
No explicit capability or integration was extracted; that does not mean none exists.
Declares a dependency on zod.
package.json:60Declares a dependency on @aws-sdk/client-s3.
package.json:33Declares a dependency on @cfworker/json-schema.
package.json:34Declares a dependency on @hono/node-server.
package.json:35Declares a dependency on @modelcontextprotocol/client.
package.json:36Declares a dependency on @modelcontextprotocol/server.
package.json:37A license or copying file is present; its terms have not been reviewed.
LICENSE.txt:1These are references in selected source files, not proof that a feature works at runtime.
Read from commit c5dea1a at Oct 12, 2026, 5:14 AM UTC. Source links open that exact commit. Repository statements are unreviewed and do not affect the score.
Critical details are withheld publicly for the first 30 days after a scan. A matched pattern is a lead for investigation, not a confirmed vulnerability.
Dependencies: 513 exact runtime versions from package-lock.json checked against OSV.dev on Oct 12, 2026; 5 with known advisories. Reachability is not checked.
Metal Mantra could not confirm that the owner controls the stated domain. The domain may belong to someone else.
Verify the domain using the Metal Mantra DNS TXT challenge.
@modelcontextprotocol/client 2.0.0 (npm) has a known advisory: GHSA-6qxp-vccf-f47h (highest severity high). MCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server
Upgrade to a fixed version listed in the advisory and regenerate the lockfile.
source-map-js 1.2.1 (npm) has a known advisory: GHSA-68fv-2mgg-jv7q (highest severity high). source-map-js allows event-loop denial of service through indexed source-map section offsets
Upgrade to a fixed version listed in the advisory and regenerate the lockfile.
No privacy policy link was found on the stated homepage. Buyers cannot see how the vendor handles their data.
Expose a clear Privacy Policy link on the official homepage.
No terms link was found on the stated homepage. Buyers cannot see the conditions that apply to using the service.
Expose a clear Terms link on the official homepage.
hono 4.13.5 (npm) has a known advisory: GHSA-hxh3-vqpv-xpqv (highest severity moderate). hono/jsx renders plain strings unescaped in boundary components, leading to XSS
Upgrade to a fixed version listed in the advisory and regenerate the lockfile.
ip-address 10.7.0 (npm) has known advisories: GHSA-h3mg-xc3c-68pw, GHSA-j6r3-76f7-8jcv (highest severity moderate). ip-address: Address6 builds a parse diagnostic proportional to the input with no length bound, allowing a single long string to stall or crash the process
Upgrade to a fixed version listed in the advisory and regenerate the lockfile.
nodemailer 9.1.1 (npm) has known advisories: GHSA-6vj9-mwq6-2f5v, GHSA-8vvx-rff5-p5rq, GHSA-g57g-f23g-4646, GHSA-prgh-xp8r-p3m5, GHSA-v53p-9fqp-m79j (highest severity moderate). Nodemailer: Process-global DNS cache reuses TLS `servername` across transports, enabling cross-tenant SMTP credential disclosure
Upgrade to a fixed version listed in the advisory and regenerate the lockfile.
Each pillar starts at 100. Rule deductions reduce its score; weights determine the overall contribution.
No user reports yet.
Each report is one signed-in GitHub account saying what happened. We do not verify that the account ran the agent, and reports never change the automated score or grade. For a security problem, use the disclosure page instead of a public note.
Share the full report so its scope and limits travel with the score.