Limitations

Hierophant reduces guesswork. It does not replace your own review or an isolated environment.

A result is not a guarantee

No issues found means the rules in one ruleset version matched nothing at one commit. It does not prove that a repository is harmless.

What it can miss

  • Payloads reworded or hidden in ways the rules do not recognize.
  • Malicious application code outside agent files and the scripts they launch.
  • Package code, which is not downloaded or analyzed. Package checks rely on public advisory data, which can be late or incomplete.
  • Dependencies listed in lockfiles or manifests, which are not checked.
  • Content that a script fetches from the network when it runs.
  • Files skipped because of size, count, time limits, symbolic links, or submodules.
  • Agents and configuration formats that are not supported yet.

What it can get wrong

A finding can be a false positive. A legitimate setup hook and a malicious one can look similar. Read the flagged line before you decide.

Agent behavior changes

Open Impact relies on vendor documentation at the time it was last checked. Vendors can change how their agents work, and your own settings can change the outcome.

A report describes one commit

A later commit can add something new. Scan again before you trust an updated repository.

Only public GitHub repositories

Private repositories and other Git hosts are not supported.