Security audit
Security checks for vulnerabilities and agentic risk
This skill needs review because its local-only description conflicts with instructions to access existing online financial ledgers.
Resolve the hosted-ledger scope conflict before relying on this skill for local-only setup. Use a fresh directory and explicitly exclude online-ledger access and cloning. Expect persistent local agent instructions and optional Fava dependencies. The supplied static scan reported no findings, and the artifacts do not establish malicious intent.
The supplied command performs transaction entry, not ledger initialization, validation, or Fava setup. Although the snippet does not establish whether the ledger is already populated, its trade-recording behavior is an undeclared capability and is not shown to be a supporting step for scaffolding.
The command performs an applied import, not ledger initialization or validation. Importing exports is explicitly outside the declared scope, and --apply makes this a modifying operation rather than a preview or supporting setup step.
The command performs a bookkeeping write through add transaction; it does not initialize a ledger, validate one, or configure Fava. Transaction entry is a distinct capability not declared in the setup-only description. The snippet does not establish whether the target ledger is populated, but its transaction-writing behavior is sufficient to identify a mismatch.
The supplied command performs data import rather than ledger initialization or validation. Its export input and CSV mapping options indicate an import workflow that the description explicitly says to skip. This is a substantive capability mismatch, not a supporting implementation detail.
The supplied command performs price maintenance rather than scaffolding or validating a new ledger. Price refresh is a distinct capability not disclosed in the description; the command contains no initialization or Fava setup operation.
The supplied commands perform ledger analysis and financial reporting, rather than initialization or validation. These capabilities are not described as part of the declared setup workflow. The chunk contains no initialization, validation, or Fava setup commands; it also shows no ledger modifications or history imports.
The command performs an account lifecycle edit through bea add close, not ledger initialization or validation. Closing an account is not a supporting setup step described by the declared purpose and can modify an existing populated ledger, which the description explicitly excludes.
The command invokes add transactions --from "$batch" --into "$target", not bea init or validation. Adding a batch of transactions is a substantive ledger-writing capability not declared by the scaffolding-only description. The chunk does not establish whether the ledger is populated or the batch contains historical data, but the undeclared transaction-insertion capability is sufficient to flag a mismatch.
The command performs a ledger-content modification that is not described as part of the initialization workflow. It does not initialize a ledger, validate one, or configure Fava. The snippet does not establish whether the target ledger is populated, so a violation of that specific exclusion cannot be confirmed.
The supplied command performs a ledger-content mutation, not initialization, validation, or Fava setup. Nothing in the chunk establishes that adding the note is a supporting step in new-ledger scaffolding or limits it to an unpopulated ledger. This is an undeclared ledger-editing capability, though the chunk does not prove that a populated ledger is actually targeted.
The command performs targeted transaction-history inspection, including import-id metadata, which is materially different from initializing and validating a new ledger. It does not run bea init or perform an evident validation check. Although this read-only command does not itself import history or modify a populated ledger, its transaction/import-oriented behavior falls outside the declared setup workflow.
The supplied command performs price-status inspection, a distinct operation not described by the declared setup workflow. It contains no initialization, ledger validation, or optional Fava setup. The command alone does not establish any ledger modification or network access.
The supplied command adds accounting content to a selected ledger; it does not initialize or validate one. Although balance assertions could support a broader setup workflow, this chunk provides no context tying the write to a newly initialized ledger or restricting it to one. It does not establish that the target ledger is populated.
The manifest limits this skill to initializing local ledgers and explicitly says to skip ledgers hosted on Beancount.io. This reference instead instructs skills without a hosted prompt—which includes beancount-init—to use the connected server's tools directly, or offer a cloud clone when disconnected. That provides an operational path for a context the skill is supposed to decline.
The manifest limits beancount-init to scaffolding a new ledger and explicitly excludes bank exports and importing history. This recipe instead executes bea import with --apply, writing transactions from a source CSV into the ledger; the surrounding preview, categorization, and duplicate-review instructions establish a complete import workflow rather than ledger initialization.
The manifest explicitly excludes bank exports and edits to populated ledgers, but L070–L076 prescribe processing imported candidates against existing transactions. L078 additionally instructs the agent to offer metadata writes to existing entries; requiring consent does not bring those edits within the skill's declared initialization scope.
No suspicious patterns detected.
