ovecc
NPM · OVECC · SCANNED AUG 8
Architecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate
Available components
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 →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Ovecc-labs/ovecc). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Stability & Change Management0
- Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.Unverified
Tool Coverage0
- Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.Unverified
Capabilities0
- Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · ovecc
claude mcp add ovecc-labs-ovecc -- npx -y ovecc
codex mcp add ovecc-labs-ovecc -- npx -y ovecc
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ovecc-labs-ovecc": {
"type": "local",
"command": [
"npx",
"-y",
"ovecc"
],
"enabled": true
}
}
} openclaw mcp add ovecc-labs-ovecc --command npx --arg -y --arg ovecc
mcp_servers:
ovecc-labs-ovecc:
command: "npx"
args: ["-y", "ovecc"] {
"mcpServers": {
"ovecc-labs-ovecc": {
"command": "npx",
"args": [
"-y",
"ovecc"
]
}
}
} 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.
- 8 Aug 26 50
First indexed and scored.
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 8 Aug 2026 · Analysed npm/[email protected]
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 | Ovecc-labs/ovecc |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Ovecc-labs/ovecc/.github/workflows/ci.yml@refs/tags/v0.2.4 |
| Rekor log index | 2375830800 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:505d96993564c643c4ac498c862285778b33244a8f8c40cb7f4d5d34ff2696ebfde93f711cb63cf7f0e26fbcbfbd81a413b27fdad4532622626fe93c2 |
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
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.
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.