Elsas Verify — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Elsas Verify (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Independently verify the daily security-intelligence reports published by [elsas.it](https://elsas.it) — offline, with no trust in our servers and no access to our keys.
elsas.it is a daily, signed security-intelligence service for AI-agent stack operators: CVEs, supply-chain incidents and advisories (GHSA · CISA-KEV · OSV · NVD · national-CERT feeds) assessed for impact on MCP servers, LLM proxies and agent orchestration — curated, cross-validated, and Ed25519-signed. Served as a paid MCP tool for $0.10 USDC via the x402 payment protocol.
This repository contains everything a third party needs to prove a report is authentic and untampered — our public key, the JSON schema, a real signed sample report, and a dependency-free verification script. Nothing here is secret; every file is also served live from elsas.it. The point is simple:
Don't trust us — verify.
Requirements: openssh-client (ssh-keygen) and python3 — present on any Linux/macOS. No install, no network needed for the verification itself.
git clone https://github.com/romans-repos/elsas-verify.git
cd elsas-verify
./verify-report.sh examples/sample-report.json allowed_signersExpected output:
VALID: authentic & untampered
Signer: [email protected]
Hash: sha256:…
Good "elsas-report" signature for [email protected] with ED25519 key SHA256:gLVNll72kb8Iyni2vNMR6oHGqVh0Ynz+lBMhbS+cSa4# Fetch the current public sample + its detached signature
curl -s https://elsas.it/sample > report.json
curl -s https://elsas.it/.well-known/report.json.sig > report.json.sig
# Verify against the pinned key in this repo
./verify-report.sh report.json allowed_signersYou can also verify by hand with stock OpenSSH:
ssh-keygen -Y verify \
-f allowed_signers \
-I [email protected] \
-n elsas-report \
-s report.json.sig < report.jsonssh-keygen -Y sign. Verification isoffline and zero-trust: you hold the payload, you verify locally.
allowed_signers — our publickey, identity-pinned to [email protected]. A substituted signers file with a different key is rejected by the -I flag.
curl -s https://elsas.it/.well-known/allowed_signersKey fingerprint: SHA256:gLVNll72kb8Iyni2vNMR6oHGqVh0Ynz+lBMhbS+cSa4
_integrity.content_hash (sha256 over thecanonical JSON) for tamper evidence — see SIGNATURE-VERIFY.md.
| File | Purpose |
|---|---|
verify-report.sh | Dependency-free verifier (ssh-keygen + python3 stdlib) |
allowed_signers | Our public signing key — the root of trust |
schemas/report-v4.json | JSON schema of a report payload |
examples/sample-report.json (+ .sig) | A real, signed report to verify against |
SIGNATURE-VERIFY.md | The full verification recipe and trust details |
This repo is the verification surface only. The curation pipeline, scoring prompts, relevance taxonomy, infrastructure and any operational configuration are intentionally not published — they are neither needed to verify a report nor useful to a third party. Verifiability does not require disclosing how the sausage is made; it requires that the result is checkable. That's what this is.
Tooling in this repository is released under the MIT License. Report payloads themselves carry their own license terms inside the report (_integrity._license_coverage).
Service: https://elsas.it · Docs: https://elsas.it/docs · Sample: https://elsas.it/sample
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.