Evidence-backed codebase understanding with file:line citations, for AI clients over MCP.
La vérification confirme l’identité de l’éditeur (la propriété du dépôt), pas la sûreté du code. L’analyse de sécurité couvre les CVE connues et les scripts d’installation suspects.
Lu dans le code que npm livre réellement, au moment de l’analyse. Le paquet n’a jamais été exécuté. Les outils enregistrés dynamiquement à l’exécution, ou cachés dans du code empaqueté ou minifié, peuvent passer inaperçus — c’est donc un plancher de la surface d’outils, pas un recensement complet.
rune_rescanRe-scan the project from disk and refresh Rune's understanding graph. Call this after significant code changes if `rune watch` isn't already running in the background.Re-scan the project from disk and refresh Rune's understanding graph. Call this after significant code changes if `rune watch` isn't already running in the background.
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_get_overviewGet a high-level architecture summary of the software: detected stack, component count, route count. Start here.Get a high-level architecture summary of the software: detected stack, component count, route count. Start here.
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_list_componentsList all React components Rune has identified, with file location and detection kind (function/class).List all React components Rune has identified, with file location and detection kind (function/class).
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_list_routesList all API/page routes Rune has identified across Express and Next.js (pages + app router).List all API/page routes Rune has identified across Express and Next.js (pages + app router).
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_searchSearch facts and derived understanding by name, file path, or route path substring. Use this to find where something lives before reading files directly.Search facts and derived understanding by name, file path, or route path substring. Use this to find where something lives before reading files directly.
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_explainGiven a fact or derived-conclusion id (as returned by other rune_ tools), return the full evidence trail: the raw fact(s) it's based on, file, line, and matched source text.Given a fact or derived-conclusion id (as returned by other rune_ tools), return the full evidence trail: the raw fact(s) it's based on, file, line, and matched source text.
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_get_file_dependenciesGet the internal (relative-import) dependency list for a given file path, as recorded in the understanding graph.Get the internal (relative-import) dependency list for a given file path, as recorded in the understanding graph.
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_get_memoryGet durable project-specific knowledge Rune has recorded: conventions, required commands, known pitfalls. Each entry has a status (proposed/approved/rejected) and confidence score -- only 'approved' entries should be treated as trusted; 'proposed' entries are unverified and should be treated as a h…Get durable project-specific knowledge Rune has recorded: conventions, required commands, known pitfalls. Each entry has a status (proposed/approved/rejected) and confidence score -- only 'approved' entries should be treated as trusted; 'proposed' entries are unverified and should be treated as a h…
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_get_experienceGet the history of past task attempts recorded for this project: what was tried, whether it succeeded or failed, and why. This is raw history, not verified rules -- use rune_get_memory for trusted, approved conventions.Get the history of past task attempts recorded for this project: what was tried, whether it succeeded or failed, and why. This is raw history, not verified rules -- use rune_get_memory for trusted, approved conventions.
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_get_security_findingsGet all security findings Rune has detected in this project: exposed secrets, dangerous shell execution, risky CI/CD workflow permissions, and typosquat-shaped dependencies. Use this before merging a PR or reviewing a codebase for security risk -- this is the single call that answers 'are there sec…Get all security findings Rune has detected in this project: exposed secrets, dangerous shell execution, risky CI/CD workflow permissions, and typosquat-shaped dependencies. Use this before merging a PR or reviewing a codebase for security risk -- this is the single call that answers 'are there sec…
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_verify_factRe-check a single fact (by id, as returned by other rune_ tools) against the current state of its source file, instead of trusting what was recorded at the last `rune scan`. Returns 'confirmed' if the code still matches, 'stale' with both the old and new evidence lines if it changed, or 'file_missi…Re-check a single fact (by id, as returned by other rune_ tools) against the current state of its source file, instead of trusting what was recorded at the last `rune scan`. Returns 'confirmed' if the code still matches, 'stale' with both the old and new evidence lines if it changed, or 'file_missi…
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_check_driftRe-check every fact in the graph against the live state of the code and summarize how much has drifted since the last `rune scan`. Cheap: re-reads only the specific line each fact points to, not a full re-parse of the project. Use this to decide whether the current graph is still trustworthy before…Re-check every fact in the graph against the live state of the code and summarize how much has drifted since the last `rune scan`. Cheap: re-reads only the specific line each fact points to, not a full re-parse of the project. Use this to decide whether the current graph is still trustworthy before…
Aucun schéma d’entrée n’a été publié pour cet outil.
rune_agentAucune description publiéeCet outil n’a publié aucune description. Forge n’en invente pas.
12 outils sur 13 ont publié une description.
Les noms et descriptions d’outils sont écrits par l’éditeur et affichés tels quels, comme du texte inerte. Ce sont les chaînes qu’un client MCP transmet à un modèle, alors Forge y recherche des motifs d’injection de prompt — tout constat apparaît avec l’analyse de sécurité ci-dessus. « Privilégié » est une correspondance de mot-clé sur le nom de l’outil, pas un audit de ce qu’il fait : un nom anodin peut tout de même tout faire.
Evidence-backed codebase understanding with file:line citations, for AI clients over MCP.
Les noms cliquables ouvrent l’index Forge de toutes les entrées observées exposant cet outil. Parcourir tous les outils indexés.
Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.