toml_path_absent

Assert a JSONPath query over the document matches nothing; one file-level violation if present.

Semantics:

The query must select zero nodes. Any match fires exactly one violation for the file — never per-match, so a $[?…] filter that fans out over every top-level key still yields a single violation.
The existence sibling of the value-checking kinds; mirrors file_absent for a path. equals / matches / if_present don’t apply.
Useful for forbidding a key: a postinstall script in package.json, a [patch] table in Cargo.toml, or write-all permissions in a workflow.

Options

Option	Type	Required	Default	Description
`path`	string	yes		`JSONPath` expression rooted at `$`. The rule fires one violation per file if the query matches any node (the path must be absent).

Plus the common paths, level, id, and when fields. This table is generated from the JSON Schema; option types and defaults are authoritative.

Example

A Cargo.toml that overrides a dependency via [patch]

The rule fires on this repository:

Cargo.toml

[package]
name = "demo"
version = "0.1.0"

[patch.crates-io]
serde = { git = "https://github.com/example/serde" }

With this .alint.yml:

version: 1
rules:
  - id: no-cargo-patch
    kind: toml_path_absent
    paths: "Cargo.toml"
    path: "$.patch"
    level: error
    message: >-
      Cargo.toml carries a `[patch]` table; patched dependencies are easy to
      forget and hard to audit. Prefer a normal version requirement.

alint check reports:

--- Cargo.toml -----------------------------------------------------------------
  x  error    no-cargo-patch
              Cargo.toml carries a `[patch]` table; patched dependencies are
              easy to forget and hard to audit. Prefer a normal version
              requirement.

Summary (1 violation):
  x 1 error
  0 passing * 1 failing

A Cargo.toml with only normal dependencies

This repository is compliant:

Cargo.toml

[package]
name = "demo"
version = "0.1.0"

[dependencies]
serde = "1"