Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

Sundeepg98/google-docs-mcp

https://github.com/Sundeepg98/google-docs-mcp · scanned 2026-06-16 04:39 UTC (1 month, 3 weeks ago)

3 raw signals (0 security + 3 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 3 weeks ago · v1 · 3 actionable findings from 1 signal source. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 92.6/100 with 77.8% coverage. It contains 30 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 3 findings — concentrated in hardware (1), cicd (1), quality (1). Risk profile is low: 0 critical, 0 high, 2 medium. Recommended next step: open the hardware layer findings first — that's where the highest-impact wins live.

Showing 3 of 3 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing
AI-coder instruction files were found, but the repo is missing ci. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.
Repo hardeningGenerated repo pattern
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: litestream/litestream:0.5.12
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
Dockerfile:11 containersPinned dependencies
For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.
For AI agents + API integrations
Email me when this repo regresses
Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.
API access

This page is publicly accessible at: https://repobility.com/scan/e2e7bf86-95f6-4243-bce1-902823eec0b7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/e2e7bf86-95f6-4243-bce1-902823eec0b7/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.