Effectue des scans de sécurité en langage naturel sur les applications conçues par IA et génère des demandes de correction pour les agents de codage.
Aussi connu sous contentasoftware/appledger
- Étoiles
- 0
- Outils
- —
- Téléchargements, 30 jours
- —
- Dernière version
- 0.2.5
- Dernier commit
- 14 oct. 2026
- Licence
- MIT
Qu'est-ce que AppLedger MCP ?
Effectue des scans de sécurité en langage naturel sur les applications conçues par IA et génère des demandes de correction pour les agents de codage.
Résumé généré à partir du README du projet
À propos du MCP server AppLedger
AppLedger fournit un retour d'expérience de sécurité pour les applications construites à l'aide d'outils d'IA tels que Claude Code, Cursor et Lovable. Il analyse les dossiers d'application en utilisant des outils indépendants pour identifier les vulnérabilités et traduit les découvertes techniques en anglais simple. Le service aide les développeurs à comprendre ce qui ne va pas, pourquoi c'est important et comment le corriger. Il génère également un fichier fix-prompt.md spécifique qui peut être transmis directement à un agent de codage pour résoudre les problèmes.
Les utilisateurs peuvent choisir entre un mode hébergé ou un mode local. En mode hébergé, les fichiers que Git committerait sont compressés et envoyés via HTTPS à appledger.net pour analyse, tandis que les fichiers sensibles comme .env ou les clés SSH sont strictement exclus. Le mode local conserve tout le code sur votre machine en utilisant des versions installées de Trivy et Opengrep. Le système utilise Trivy pour trouver les clés divulguées et les bibliothèques obsolètes, tandis qu'Opengrep détecte les modèles dangereux comme l'injection SQL. Pour ceux qui possèdent déjà un serveur SonarQube, le mode local peut optionnellement inclure ces scans pour vérifier la qualité du code et les points sensibles de sécurité.
Ce que vous pouvez faire avec
- 1Générer des demandes de correction pour l'IACréez un fichier markdown contenant un ensemble d'instructions prêtes à l'emploi que vous pouvez donner à un agent de codage pour réparer les failles de sécurité.
- 2Auditer le code généré par IA pour détecter les vulnérabilitésScannez le dossier de votre application pour trouver des mots de passe divulgués, des bibliothèques obsolètes ou des modèles dangereux comme l'injection SQL.
- 3Automatiser les inspections de sécurité régulièresConfigurez des scans automatisés quotidiens ou hebdomadaires en utilisant des planificateurs système comme cron ou le Planificateur de tâches Windows.
Extrait du README du projet. Chaque cas d'utilisation est vérifié par rapport à une citation du document.
Comment installer AppLedger MCP
Formats vérifiés le 10 nov. 2026Ajouter à CursorAjouter à GooseInstaller AppLedger MCP dans Claude Code
$ claude mcp add --env 'APPLEDGER_KEY=<YOUR_APPLEDGER_KEY>' appledger -- uvx appledgerInstaller AppLedger MCP dans Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"appledger": {
"command": "uvx",
"args": [
"appledger"
],
"env": {
"APPLEDGER_KEY": "<YOUR_APPLEDGER_KEY>"
}
}
}
}Installer AppLedger MCP dans VS Code
.vscode/mcp.json
{
"servers": {
"appledger": {
"type": "stdio",
"command": "uvx",
"args": [
"appledger"
],
"env": {
"APPLEDGER_KEY": "<YOUR_APPLEDGER_KEY>"
}
}
}
}Installer AppLedger MCP dans VS Code CLI
$ code --add-mcp '{"name":"appledger","type":"stdio","command":"uvx","args":["appledger"],"env":{"APPLEDGER_KEY":"<YOUR_APPLEDGER_KEY>"}}'Installer AppLedger MCP dans Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"appledger": {
"command": "uvx",
"args": [
"appledger"
],
"env": {
"APPLEDGER_KEY": "<YOUR_APPLEDGER_KEY>"
}
}
}
}Installer AppLedger MCP dans Codex
$ codex mcp add appledger --env 'APPLEDGER_KEY=<YOUR_APPLEDGER_KEY>' -- uvx appledgerInstaller AppLedger MCP dans Codex config.toml
~/.codex/config.toml
[mcp_servers.appledger] command = "uvx" args = ["appledger"] [mcp_servers.appledger.env] APPLEDGER_KEY = "<YOUR_APPLEDGER_KEY>"
Installer AppLedger MCP dans Gemini CLI
$ gemini mcp add -s user -e 'APPLEDGER_KEY=<YOUR_APPLEDGER_KEY>' appledger uvx -- appledgerInstaller AppLedger MCP dans Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"appledger": {
"command": "uvx",
"args": [
"appledger"
],
"env": {
"APPLEDGER_KEY": "<YOUR_APPLEDGER_KEY>"
}
}
}
}Configuration
APPLEDGER_KEYSecretOptional dashboard connection key (al_...). Without it, nothing goes to a dashboard; a hosted check returns a link that saves its result to a free account (the summary is kept up to 24 hours).
APPLEDGER_MODEhosted (default): files Git would commit are sent to appledger.net, scanned and deleted. local: Trivy and Opengrep run on this machine.
| Nom | Description | Type |
|---|---|---|
| APPLEDGER_KEY | Optional dashboard connection key (al_...). Without it, nothing goes to a dashboard; a hosted check returns a link that saves its result to a free account (the summary is kept up to 24 hours). | Secret |
| APPLEDGER_MODE | hosted (default): files Git would commit are sent to appledger.net, scanned and deleted. local: Trivy and Opengrep run on this machine. |
Vérifications automatisées
Exécuté le 14 nov. 2026Rapport complet →A passé nos vérifications automatisées. Il ne s'agit pas d'un audit de sécurité : lisez le code et donnez au serveur l'accès le plus restreint dont il a besoin. Fonctionnement des vérifications
- Dépôt source lié et accessiblecontentasoftware/appledger is public and reachablegithub.com/contentasoftware/appledger ↗Réussi
- Le nom du package correspond au dépôt sourceappledger names contentasoftware/appledger as sourcepypi.org/project/appledger/ ↗Réussi
- Provenance du build (attestation Sigstore)Sigstore attestation for appledgerpypi.org/project/appledger/ ↗Réussi
- Licence open source (OSI)MITspdx.org/licenses/MIT.html ↗Réussi
- Commit ou version publiée au cours de l'année écouléeLast commit or release 2026-10-14github.com/contentasoftware/appledger ↗Réussi
- OpenSSF ScorecardNon vérifié
- Nom du package non proche d'un package populaireNo popular package one edit away from appledgerRéussi
- Aucun avis critique dans le package ou ses dépendances32 resolved dependencies checked; no critical advisoryosv.dev ↗Réussi
- Aucune instruction cachée destinée au modèle0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersRéussi
- Les outils destructifs sont étiquetésNon vérifié
- Le point de terminaison distant répond à la poignée de main MCPNon vérifié
README
Voir sur GitHubAppLedger honest check
Honest security feedback, in plain language, for apps people build with AI tools such as Claude Code, Codex, Cursor and Lovable.
AppLedger checks your app folder with independent scanners and explains what they find in everyday words: what is wrong, why it matters, and what to do. It also writes a fix request you can hand straight to the AI tool that built the app, then checks again.
What it checks
| Scanner | Finds |
|---|---|
| Trivy | Leaked passwords and keys, outdated libraries with known security problems, risky container setup |
| Opengrep | Dangerous code patterns: SQL injection, command injection, unsafe data loading, debug mode left on |
| SonarQube (optional, local mode) | Code quality and more security hotspots, if you already run a SonarQube server |
Each run produces, in <your-app>/.appledger/:
report.html: a score, who may use the app right now (only you, your team, the whole company), and every problem in plain wordsfix-prompt.md: a ready-made fix request for your coding agentfindings.json: the same findings for tools and dashboards
Two ways to run
| Mode | What you install | Where your code goes |
|---|---|---|
| Hosted (default) | Only this package | Source files Git would commit are zipped, sent over HTTPS to appledger.net, scanned and deleted right after. Secret files are never sent. You confirm before the first upload of each folder |
Local (--local or APPLEDGER_MODE=local) |
Also Trivy, Opengrep and the Opengrep rules | Stays on your computer. With a connection key, only a summary goes to your dashboard (see below); --no-dashboard skips even that |
What gets uploaded in hosted mode
- Sent: files Git would commit (
git ls-files, including new files that aren't ignored). Outside a Git repository,.gitignoreis still honoured. - Never sent:
.envand.env.*(except.env.example,.env.sample,.env.template),*.pem,*.key,*.p12,*.pfx, SSH keys,.npmrc,.pypirc,.netrc,*credentials*.json,service-account*.json,secrets.*, the folderscert,certs,secrets,.sshand.aws,.claude/settings.local.json, Terraform state, password files, Ansible Vault files, Kubernetes/Helm secret manifests, certificates and similar (full list insrc/appledger/uploadpolicy.py). The server drops such files again as a second safety net. - Skipped: dependencies, build output, media, documents and data files (CSV, spreadsheets, slides, SQL, logs, data dumps) and files over 1 MB.
If a secret file is committed to Git or not ignored, the check reports it as a problem by file name. Its content is never read or sent.
See exactly what would be sent, and what is left out and why, without uploading anything:
python -m appledger path/to/your-app --list-files
The first hosted check of a folder asks you to confirm. In scripts and scheduled runs, pass --yes. If the code belongs to your employer or a client, make sure you're allowed to upload it, or use local mode.
Install
Claude Code plugin (recommended: adds the guided check-my-app skill):
claude plugin marketplace add contentasoftware/appledger
claude plugin install appledger@appledger
In the Claude Code desktop app, add the marketplace contentasoftware/appledger in the plugin settings instead. Start a new session, then ask: "Is my app safe to share?" or "Add this app to AppLedger".
MCP server only (needs uv):
claude mcp add appledger -- uvx --from appledger appledger-mcp
Command line:
pip install appledger
python -m appledger path/to/your-app
Step-by-step guide with troubleshooting: https://appledger.net/docs/
Version 0.2.0 (upload preview, consent, secret-file exclusion, scheduling) is being released to PyPI; until then pip install appledger gets 0.1.x.
Company dashboard
Create a free account at appledger.net to keep every app your people check in one ledger: owner, grade, score trend, who may use it and which AI tool built it. Create a connection key under "Connect a computer", then save it on each computer:
python -m appledger --connect al_your_key
Or tell Claude: "Connect AppLedger with this key: al_…". The key is saved in ~/.appledger/key; APPLEDGER_KEY overrides it and --disconnect removes it.
From then on each check also saves a summary to your dashboard: the app's name, score, grade, problem counts, the list of problems found (level and short title, up to 60; never code or file paths), and the scanners used. Never the code.
Not connected yet? From 0.2.3, a hosted check from a computer without a key ends with a save link, also shown in report.html:
Save this result to a free AppLedger ledger (link works for 24 hours): https://appledger.net/app/claim.php?t=...
Open it, create a free account or log in, and the check is in your ledger; the page then offers a key for that computer. Until the link is used, the service keeps only the check's summary (app name, score, the problems' levels and titles; never code), for up to 24 hours. A link works once; --no-dashboard turns it off.
You can also add an app in the web app with Add app: register it without code, or upload a zip to check it in the browser (the zip is scanned and deleted the same way).
Scheduled checks
python -m appledger path/to/your-app --schedule weekly --yes # or daily
python -m appledger --schedules # list
python -m appledger path/to/your-app --schedule off # stop
Uses Windows Task Scheduler on Windows and cron on macOS and Linux. Hosted scheduled checks need the one-time --yes consent; add --local to schedule local checks instead. --quiet prints one line per check.
Local mode setup
- Trivy:
winget install AquaSecurity.Trivy(Windows) orbrew install trivy(Mac) - Opengrep: download from the releases page and put it on your PATH
- Rules:
git clone --depth 1 https://github.com/opengrep/opengrep-rules.git ~/.appledger/opengrep-rules - Check:
python -m appledger --doctor
Repository layout
| Path | What |
|---|---|
src/appledger/scanner.py |
Scanners, plain-language translation, report and fix request |
src/appledger/client.py |
Picks the files to send (honouring .gitignore) and sends them to the hosted service |
src/appledger/uploadpolicy.py |
The full list of secret files that are never uploaded, used by client and server |
src/appledger/service.py |
Server side: unpacks an upload safely and scans it |
src/appledger/server.py |
Local MCP server used by the plugin |
plugin/ |
Claude Code / Codex plugin with the check-my-app skill |
tests/mcp_smoke.py |
Calls every MCP tool like an agent would |
License
MIT. The Opengrep community rules used by the scanner have their own license (Commons Clause); check it before using them in a paid service.
Questions sur AppLedger MCP
Comment ajouter AppLedger MCP à Claude Code ?
Exécutez claude mcp add --env 'APPLEDGER_KEY=<YOUR_APPLEDGER_KEY>' appledger -- uvx appledger dans votre terminal. Ajoutez --scope user pour le rendre disponible dans tous les projets.
Comment ajouter AppLedger MCP à Cursor ?
Ouvrez ~/.cursor/mcp.json et ajoutez le serveur sous mcpServers, avec la configuration Cursor indiquée dans la section d'installation ci-dessus.
Comment puis-je utiliser les résultats pour corriger mon code ?
L'outil génère un fichier fix-prompt.md qui est une demande de correction prête à l'emploi que vous pouvez fournir directement à votre agent de codage IA.