properties_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, when, scope_filter, fix, and expect_matches fields. This table is generated from the JSON Schema; option types and defaults are authoritative.

Example

A .properties that leaves debug enabled

The rule fires on this repository:

application.properties
✗ error no-debug
debug.enabled is set in a production .properties; remove it.

server.port=8080
debug.enabled=true

With this .alint.yml:

version: 1
rules:
  - id: no-debug
    kind: properties_path_absent
    paths: "application.properties"
    path: "$['debug.enabled']"
    level: error
    message: >-
      debug.enabled is set in a production .properties; remove it.

alint check reports:

--- application.properties -----------------------------------------------------
  x  error    no-debug
              debug.enabled is set in a production .properties; remove it.

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

A .properties with no debug flag

This repository is compliant:

application.properties✓

server.port=8080