lockfile

ACVE lockfile

acve.lock.json is a redacted, machine-readable snapshot of an agent configuration. It records the effective harness settings and the installed versions that an audit can compare with ACVE advisories. It is not a copy of the user's configuration files.

Top level

• lockfileVersion is 1; generatedAt is UTC; generator identifies ACVE.
• scope is project or machine; root is the project root token.
• platform records the OS and Node version. fingerprint hashes canonical agents.
• harnesses records file-detected harness versions and confidence.
• agents contains one normalized configuration per scope; warnings records incomplete coverage.

Redaction rules

| Input | Stored value | | --- | --- | | Environment | Sorted key names only (envKeysSet) | | Commands and arguments | Hash, basename, and safe argument summary | | URLs | Scheme, host, and port; never credentials or query values | | Secret-looking strings | <redacted> / omitted before hashing | | Credential, auth, token, key, certificate, and .env files | Never read | | Paths | Home and known application directories become stable tokens |

Paths, timestamps, and machine-specific locations are excluded from configurationId. All hashes use the sha256:<64 lowercase hex> form. Unknown versions remain unknown; they are not guessed by executing discovered commands.

Agent fields

permissionMode, sandbox, trust, model/effort, instruction and settings files, MCP servers, hooks, plugins, skills, tool allow/deny lists, environment key presence, features, rules, and source hashes describe security-relevant behavior. package is a package URL when a server can be resolved, otherwise null; registryName preserves a separate MCP registry identity.