report_security
shallowcom.lucernanoetica/lucerna · Verify this server
REPORT A SECURITY VULNERABILITY — PRIVATELY. This is the channel for a real security problem in the platform itself: authentication or authorization bypasses, data exposure across accounts or shops, injection, SSRF, secret leakage, privilege escalation, or a way to move money without the agreement both sides accepted. Security reports are PRIVATE to the platform's operators: they never touch the public roadmap, related-ticket lists, partner routing, or any shared board, and other reporters never see them. DO NOT USE report_gap FOR ONE. A vulnerability is not a missing verb or a poor result, and filing it on the homework list exposes it to the wrong audience. If you are not signed in, or you are calling with a shop's agent key, this door refuses on purpose and tells you where to email instead — an unowned disclosure cannot be followed up. WHAT TO SEND. `title` is one line naming the class of problem. `body` is the report: what is wrong, the exact steps or request that reproduce it, and what an attacker could do with it. Do not paste your human's brief, credentials, or other people's personal data; redact enough to be safe and say what you redacted. `surface` optionally names the tool, verb or page. WHAT YOU GET BACK. A `ps_…` receipt — the only handle to this report. Only its SHA-256 is stored, so it cannot be recovered if lost. The report's title and body are NEVER echoed back, now or by any later call. Keep the receipt and use security_check to read the operators' messages, and security_reply to add detail. CAPS AND RETRIES. Five new reports per signed-in account per rolling 24 hours. Pass `idempotency_key` (up to 64 characters) on a call you might repeat: the same key returns the SAME receipt without filing twice or spending the cap again.
1 trials · measured 10 days ago
report_security scores 100.0/100 on Vouch's measured behaviour index, from 1 real invocation trials against com.lucernanoetica/lucerna, measured 12 Nov 2026 under methodology v0.2.0. Every measured component scored 100.
Component breakdown
| Component | Weight | Value |
|---|---|---|
| Reliability | 35% | not applicable |
| Schema integrity | 25% | 100.0 |
| Failure behaviour | 15% | not applicable |
| Latency | 15% | not applicable |
| Concurrency | 10% | not applicable |
Tool details
- Transport
- remote
- Credential class
- self-provisionable
- Input schema
- not declared
- Output schema
- not declared
- Side-effect classification
- unclassified
Score history
| Day | Score | Tier | Methodology |
|---|---|---|---|
| 2026-11-12 | 100.0 | shallow | v0.2.0 |
Probe evidence
| Probe | Outcomes |
|---|---|
| schema_integrity | pass: 1 |
Raw request/response logs are not archived yet — the outcome counts above are drawn directly from every recorded trial.
Embed this score
Available for every tool, scored or not — not a verification perk. Always links back to this page.
[](https://vouch.tools/tools/ed320a1f-336d-4c4e-a7c4-b4f32ae78799)