Behavioral rules · 2026.10.27
Inspect the exact rule.
This reference is generated from BuiltinRuleCatalog for ruleset 2026.10.27. Package and file-hash advisories use a separate intelligence snapshot. A rule match is evidence to review, not a guarantee about the repository.
repyy rules catalog --format json exports this versioned behavioral catalog.
Browse 147 rule definitions
Showing 147 rules.
AGENT-001 · AI-agent configuration requests automatic command execution
agent-execution · high severity · medium confidence · review
This rule identifies agent execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: AGENTS.*, CLAUDE.*, *.md, *.mdc, *.markdown, *.mdx, *.json, *.yaml, *.yml, *.toml, .cursorrules, .clinerules, .windsurfrules · Context downgrade: allowed
AGENT-002 · Instruction attempts to override agent safety or expose secrets
prompt-injection · high severity · medium confidence · review
This rule identifies prompt injection behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: AGENTS.*, CLAUDE.*, *.md, *.mdc, *.markdown, *.mdx, *.txt, .cursorrules, .clinerules, .windsurfrules · Context downgrade: allowed
APT-001 · BeaverTail or InvisibleFerret filesystem indicator
contagious-interview · high severity · high confidence · review
This rule identifies contagious interview behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
ARCHIVE-001 · Archive entry escapes its extraction root
archive-traversal · critical severity · high confidence · block
This rule identifies archive traversal behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not extract the archive.
Scope: structured · Paths: archive entries · Context downgrade: allowed
AUTORUN-001 · Directory-entry environment hook can execute repository-controlled commands
directory-auto-execution · high severity · medium confidence · review
This rule identifies directory auto execution behavior that can affect repository trust or execution safety.
Legitimate use: Development environment tools run reviewed setup commands when a trusted environment is entered.
Review action: Review the complete .envrc before approving it with direnv.
Scope: raw · Paths: .envrc · Context downgrade: allowed
AUTORUN-002 · Nix development shell defines a shell hook
development-shell-execution · medium severity · high confidence · review
This rule identifies development shell execution behavior that can affect repository trust or execution safety.
Legitimate use: Development environment tools run reviewed setup commands when a trusted environment is entered.
Review action: Inspect the shellHook before entering the Nix development shell.
Scope: raw · Paths: shell.nix, flake.nix · Context downgrade: allowed
BACKDOOR-001 · Request-controlled input reaches command execution
backdoor · critical severity · high confidence · block
This rule identifies backdoor behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: code · Paths: ** · Context downgrade: allowed
BACKDOOR-002 · Hardcoded authentication bypass or universal credential
auth-bypass · high severity · medium confidence · review
This rule identifies auth bypass behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: ** · Context downgrade: allowed
BINARY-001 · Compiled executable content is present
compiled-binary · high severity · high confidence · review
This rule identifies compiled binary behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the binary provenance and hash before use.
Scope: structured · Paths: ** · Context downgrade: allowed
BUILD-001 · CMake configuration executes an external command
build-command · medium severity · high confidence · review
This rule identifies build command behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the command, arguments, inputs, and build phase before configuring or building the project.
Scope: raw · Paths: CMakeLists.txt, *.cmake · Context downgrade: allowed
BUILD-002 · Meson configuration executes an external command
build-command · medium severity · high confidence · review
This rule identifies build command behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the command and generated outputs before configuring or building the project.
Scope: raw · Paths: meson.build, meson_options.txt · Context downgrade: allowed
BUILD-003 · Bazel rule declares a shell command
build-command · medium severity · medium confidence · review
This rule identifies build command behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the declared command and its inputs before running Bazel.
Scope: raw · Paths: BUILD, BUILD.bazel, WORKSPACE, WORKSPACE.bazel, *.bzl · Context downgrade: allowed
BUILD-004 · Make evaluates a shell command while reading the build file
build-command · high severity · high confidence · review
This rule identifies build command behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the shell expression before invoking Make, including during dry runs and variable expansion.
Scope: raw · Paths: Makefile, makefile, GNUmakefile, *.mk · Context downgrade: allowed
CHAIN-001 · Remote download piped into a command interpreter
download-execute · critical severity · high confidence · block
This rule identifies download execute behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
CHAIN-002 · Encoded content decoded and executed
decode-execute · critical severity · high confidence · block
This rule identifies decode execute behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
CHAIN-003 · Downloaded file is made executable and launched
download-execute · critical severity · medium confidence · review
This rule identifies download execute behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
CHAIN-004 · Downloaded file is executed later in the same script
staged-download-execute · critical severity · high confidence · block
This rule identifies staged download execute behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run until the downloaded content, destination, and execution path are verified.
Scope: structured · Paths: ** · Context downgrade: allowed
CICD-001 · Privileged pull_request_target workflow checks out untrusted pull-request code
ci-workflow-injection · critical severity · high confidence · block
This rule identifies ci workflow injection behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: *.yml, *.yaml · Context downgrade: allowed
CICD-002 · CI workflow interpolates untrusted event data into a shell command
ci-secret-exposure · high severity · medium confidence · review
This rule identifies ci secret exposure behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: *.yml, *.yaml · Context downgrade: allowed
CICD-003 · GitHub Action is referenced by a mutable tag or branch
ci-workflow-integrity · high severity · high confidence · harden
This rule identifies ci workflow integrity behavior that can affect repository trust or execution safety.
Legitimate use: Version tags are common and convenient, but they are not immutable.
Review action: Pin third-party actions to a reviewed full commit SHA.
Scope: structured · Paths: *.yml, *.yaml · Context downgrade: allowed
CICD-004 · CI command sends a secret to an external endpoint
ci-secret-exposure · critical severity · high confidence · block
This rule identifies ci secret exposure behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: *.yml, *.yaml · Context downgrade: allowed
CICD-005 · Non-GitHub CI configuration builds a shell command from change-controlled input
ci-workflow-injection · high severity · medium confidence · review
This rule identifies ci workflow injection behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: .circleci/config.yml, Jenkinsfile, .gitlab-ci.yml, *.gitlab-ci.yml, pipeline.yml, pipeline.yaml · Context downgrade: allowed
CICD-006 · Privileged workflow_run job executes after downloading an artifact
ci-artifact-trust · high severity · medium confidence · review
This rule identifies ci artifact trust behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Treat upstream artifacts as untrusted data; validate them and avoid executing downloaded content in this privileged job.
Scope: structured · Paths: .github/workflows/*.yml, .github/workflows/*.yaml · Context downgrade: allowed
CICD-007 · Low-trust workflow explicitly allows cache writes
ci-cache-integrity · high severity · medium confidence · review
This rule identifies ci cache integrity behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Keep low-trust jobs read-only for cache access, or verify that they cannot process untrusted input before saving a cache.
Scope: structured · Paths: .github/workflows/*.yml, .github/workflows/*.yaml · Context downgrade: allowed
CICD-008 · Pull-request workflow runs on a self-hosted runner
ci-runner-trust · high severity · medium confidence · review
This rule identifies ci runner trust behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify repository visibility, fork approval, runner isolation, and what untrusted pull-request code can access.
Scope: structured · Paths: .github/workflows/*.yml, .github/workflows/*.yaml · Context downgrade: allowed
COMBO-001 · Collection appears alongside network transfer
collection-and-exfiltration · high severity · high confidence · review
This rule identifies collection and exfiltration behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the collected data and destination before running the repository.
Scope: structured · Paths: executable source files · Context downgrade: allowed
COMBO-002 · Network retrieval appears alongside execution
fetch-and-execute · critical severity · high confidence · block
This rule identifies fetch and execute behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run until the fetched content and execution path are verified.
Scope: structured · Paths: executable source files · Context downgrade: allowed
COMBO-003 · Environment evasion appears alongside execution
evasion-and-execution · high severity · high confidence · review
This rule identifies evasion and execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the environment checks and execution path.
Scope: structured · Paths: executable source files · Context downgrade: allowed
CRED-001 · Access to sensitive credential storage
credential-harvesting · high severity · high confidence · review
This rule identifies credential harvesting behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
CRED-002 · File API reads a sensitive path
credential-harvesting · high severity · medium confidence · review
This rule identifies credential harvesting behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
DECODE-001 · A bounded literal decode reveals a rule indicator
decoded-indicator · high severity · medium confidence · review
This rule identifies decoded indicator behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the source literal and its use without executing it.
Scope: structured · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx · Context downgrade: disabled
DOC-001 · PDF declares active or embedded content
document-active-content · high severity · medium confidence · review
This rule identifies document active content behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review or remove PDF actions and embedded files before opening it.
Scope: structured · Paths: *.pdf, Office Open XML package entries · Context downgrade: allowed
DOC-002 · Office package contains a VBA macro project
office-macro · high severity · high confidence · review
This rule identifies office macro behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect or remove the macro project before opening the document.
Scope: structured · Paths: *.pdf, Office Open XML package entries · Context downgrade: allowed
DOC-003 · Office package references external content
office-external-relationship · medium severity · high confidence · review
This rule identifies office external relationship behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review and remove unneeded external relationships.
Scope: structured · Paths: *.pdf, Office Open XML package entries · Context downgrade: allowed
DOC-004 · Office document contains a Dynamic Data Exchange field
office-dynamic-data-exchange · high severity · medium confidence · review
This rule identifies office dynamic data exchange behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Remove the DDE field or inspect its command and data source.
Scope: structured · Paths: *.pdf, Office Open XML package entries · Context downgrade: allowed
DOCKER-001 · Container configuration exposes host control
container-risk · high severity · medium confidence · review
This rule identifies container risk behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: Dockerfile, Dockerfile.*, docker-compose*.yml, docker-compose*.yaml, compose*.yml, compose*.yaml · Context downgrade: allowed
DOCKER-002 · Container build downloads and immediately executes a script
container-download-execute · critical severity · high confidence · block
This rule identifies container download execute behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: Dockerfile, Dockerfile.* · Context downgrade: allowed
DOCKER-003 · Container imports remote content or mounts a sensitive host path
container-risk · high severity · medium confidence · review
This rule identifies container risk behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: Dockerfile, Dockerfile.*, docker-compose*.yml, docker-compose*.yaml, compose*.yml, compose*.yaml · Context downgrade: allowed
DOTNET-001 · MSBuild project or imported file runs a command
dotnet-build-execution · high severity · medium confidence · review
This rule identifies dotnet build execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the Exec command and its conditions before building or restoring the project.
Scope: structured · Paths: ** · Context downgrade: allowed
ENV-001 · Broad environment-variable access
environment-access · medium severity · low confidence · informational
This rule identifies environment access behavior that can affect repository trust or execution safety.
Legitimate use: Applications commonly read explicitly named configuration variables.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: code · Paths: ** · Context downgrade: allowed
EVADE-001 · Sandbox, VM, or CI evasion logic
sandbox-evasion · high severity · medium confidence · review
This rule identifies sandbox evasion behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: ** · Context downgrade: allowed
EXEC-001 · Dynamic code execution primitive
dynamic-execution · high severity · medium confidence · review
This rule identifies dynamic execution behavior that can affect repository trust or execution safety.
Legitimate use: Frameworks and developer tools sometimes evaluate generated or sandboxed code.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: code · Paths: ** · Context downgrade: allowed
EXEC-002 · Operating-system command execution
process-execution · high severity · medium confidence · review
This rule identifies process execution behavior that can affect repository trust or execution safety.
Legitimate use: Build, test, and development tooling often starts reviewed local processes.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: code · Paths: ** · Context downgrade: allowed
EXEC-003 · Browser or timer string execution primitive
dynamic-execution · high severity · medium confidence · review
This rule identifies dynamic execution behavior that can affect repository trust or execution safety.
Legitimate use: Frameworks and developer tools sometimes evaluate generated or sandboxed code.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx, *.html, *.htm · Context downgrade: allowed
EXEC-004 · Process-execution API is imported
process-capability · low severity · medium confidence · informational
This rule identifies process capability behavior that can affect repository trust or execution safety.
Legitimate use: Build, test, and development tooling often starts reviewed local processes.
Review action: Confirm that every process invocation uses fixed commands and arguments.
Scope: raw · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx, *.py · Context downgrade: allowed
EXEC-005 · PowerShell executes an encoded command
encoded-execution · critical severity · high confidence · block
This rule identifies encoded execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
EXEC-006 · Windows system utility can proxy execution or download content
proxy-execution · high severity · high confidence · review
This rule identifies proxy execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
EXECBIT-001 · File has executable permissions
executable-file · low severity · medium confidence · informational
This rule identifies executable file behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review whether this file needs to be executable.
Scope: structured · Paths: ** · Context downgrade: allowed
EXFIL-001 · WebSocket or DNS-based data transfer primitive
exfiltration · high severity · medium confidence · review
This rule identifies exfiltration behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
EXFIL-002 · Clipboard, cookie, browser-password, or keylogging access
credential-theft · high severity · medium confidence · review
This rule identifies credential theft behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
FINGERPRINT-001 · Host or user fingerprint collection
host-fingerprinting · medium severity · low confidence · informational
This rule identifies host fingerprinting behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: code · Paths: ** · Context downgrade: allowed
FLOW-001 · Axios response data reaches dynamic or process execution in the same function
remote-response-execution · critical severity · high confidence · block
This rule identifies remote response execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not execute remote response data. Review the request and execution path.
Scope: structured · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx · Context downgrade: disabled
FLOW-002 · Python remote response may reach dynamic code execution or compilation
remote-response-execution · high severity · medium confidence · review
This rule identifies remote response execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the request and execution path; do not execute untrusted remote response data.
Scope: structured · Paths: *.py, *.pyw · Context downgrade: allowed
FONT-001 · Script installs or registers fonts on the host
font-installation · medium severity · high confidence · review
This rule identifies font installation behavior that can affect repository trust or execution safety.
Legitimate use: Applications and design projects may install bundled, licensed fonts for consistent rendering.
Review action: Verify every font file and destination before allowing the script to modify host font stores.
Scope: raw · Paths: *.sh, *.bash, *.zsh, *.fish, *.ps1, *.bat, *.cmd, *.py, *.js, *.ts, *.go, *.rs, *.c, *.cc, *.cpp, *.cs · Context downgrade: allowed
FONT-002 · Binary font file requires provenance review
binary-font · medium severity · high confidence · review
This rule identifies binary font behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the font source, license, hash, and signature before installing or previewing it.
Scope: structured · Paths: *.ttf, *.otf, *.ttc, *.woff, *.woff2 · Context downgrade: allowed
FONT-003 · Font container is malformed or contains an executable payload
font-container-integrity · high severity · high confidence · review
This rule identifies font container integrity behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not install or preview the font; replace it with a trusted copy.
Scope: structured · Paths: *.ttf, *.otf, *.ttc, *.woff, *.woff2 · Context downgrade: allowed
FONT-004 · OpenType SVG glyph contains active content
font-active-content · medium severity · medium confidence · review
This rule identifies font active content behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Remove active SVG content or replace the font with a trusted copy.
Scope: structured · Paths: *.ttf, *.otf, *.ttc, *.woff, *.woff2 · Context downgrade: allowed
FONT-005 · Font contains TrueType instructions
font-program · low severity · high confidence · informational
This rule identifies font program behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify provenance before passing the instruction stream to a font engine.
Scope: structured · Paths: *.ttf, *.otf, *.ttc, *.woff, *.woff2 · Context downgrade: allowed
GITHOOK-001 · Executable Git hook or hooks-path override
git-hook · high severity · medium confidence · review
This rule identifies git hook behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: config, *.hook, pre-commit, post-checkout, post-merge, post-rewrite · Context downgrade: allowed
GITHOOK-002 · Active Git hook contains execution or remote-fetch behavior
git-hook · critical severity · high confidence · block
This rule identifies git hook behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Disable the hook and review it before running Git commands.
Scope: structured · Paths: .git/hooks/* · Context downgrade: allowed
GITHOOK-003 · Repository config installs and runs pre-commit hooks
git-hook · medium severity · high confidence · review
This rule identifies git hook behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review hook repositories, pinned revisions, entries, languages, and additional dependencies before installing the hooks.
Scope: raw · Paths: .pre-commit-config.yaml, .pre-commit-config.yml · Context downgrade: allowed
GITMETA-001 · Git configuration defines an executable filter or helper
git-metadata · critical severity · high confidence · block
This rule identifies git metadata behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: config, config.worktree, .gitattributes, attributes · Context downgrade: allowed
GO-001 · Go source declares a generator command
go-generate · medium severity · high confidence · review
This rule identifies go generate behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the generator command before running go generate.
Scope: raw · Paths: *.go · Context downgrade: allowed
GO-002 · Go module replaces a dependency source
go-module-replacement · medium severity · medium confidence · review
This rule identifies go module replacement behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: go.mod, go.work · Context downgrade: allowed
IDE-001 · Editor configuration can execute a command automatically
editor-auto-execution · high severity · high confidence · review
This rule identifies editor auto execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: tasks.json, settings.json, devcontainer.json, *.code-workspace, *.xml · Context downgrade: allowed
IDE-002 · Project-local editor configuration can execute commands, override tools, or weaken workspace safeguards
editor-auto-execution · high severity · medium confidence · review
This rule identifies editor auto execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: extensions.json, settings.json, .exrc, .nvimrc, .nvim.lua, *.vim, *.lua · Context downgrade: allowed
IDE-003 · Workspace recommends VS Code extensions
editor-extension-recommendation · low severity · high confidence · informational
This rule identifies editor extension recommendation behavior that can affect repository trust or execution safety.
Legitimate use: Teams commonly recommend reviewed editor extensions for a workspace.
Review action: Review each extension ID and publisher before choosing to install it.
Scope: raw · Paths: extensions.json, *.code-workspace · Context downgrade: allowed
IDE-004 · Repository configuration installs VS Code extensions
editor-extension-installation · medium severity · high confidence · review
This rule identifies editor extension installation behavior that can affect repository trust or execution safety.
Legitimate use: Development containers and setup scripts often provision reviewed editor extensions.
Review action: Verify the extension publisher, identifier, and source before allowing installation.
Scope: raw · Paths: devcontainer.json, *.sh, *.bash, *.zsh, *.fish, *.ps1, *.bat, *.cmd · Context downgrade: allowed
IDE-005 · Workspace task or debug configuration references an executable command
editor-command · medium severity · high confidence · review
This rule identifies editor command behavior that can affect repository trust or execution safety.
Legitimate use: Workspace tasks and debugger configurations commonly invoke reviewed project tools.
Review action: Inspect the task command, arguments, referenced scripts, and debugger configuration before running it.
Scope: raw · Paths: tasks.json, launch.json · Context downgrade: allowed
IDE-006 · Devcontainer configuration installs reusable features
devcontainer-feature-installation · medium severity · high confidence · review
This rule identifies devcontainer feature installation behavior that can affect repository trust or execution safety.
Legitimate use: Development containers commonly install reusable, reviewed tooling features.
Review action: Verify each feature source, publisher, version, and install script before creating the development container.
Scope: raw · Paths: devcontainer.json · Context downgrade: allowed
IDE-007 · Packaged VSIX editor extension is present
editor-extension-package · medium severity · high confidence · review
This rule identifies editor extension package behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the extension publisher, signature, package contents, and hash before installing it.
Scope: structured · Paths: *.vsix · Context downgrade: allowed
IDE-008 · VSIX extension declares activation or execution capabilities
editor-extension-capability · medium severity · high confidence · review
This rule identifies editor extension capability behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review activation events and contributed execution surfaces before installation.
Scope: structured · Paths: *.vsix package entries · Context downgrade: allowed
IDE-009 · VSIX extension package declares an installation lifecycle script
editor-extension-install-script · high severity · high confidence · review
This rule identifies editor extension install script behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the lifecycle command and bundled files before installation.
Scope: structured · Paths: *.vsix package entries · Context downgrade: allowed
IMAGE-001 · SVG contains active content
image-active-content · medium severity · medium confidence · review
This rule identifies image active content behavior that can affect repository trust or execution safety.
Legitimate use: Interactive SVG assets may intentionally contain script or event handlers.
Review action: Review the SVG source and remove unneeded scripts, event handlers, or JavaScript links.
Scope: structured · Paths: *.svg · Context downgrade: allowed
IMPORT-001 · Dynamic import or require assembled at runtime
dynamic-import · high severity · medium confidence · review
This rule identifies dynamic import behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: code · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx, *.py, *.java, *.kt · Context downgrade: allowed
IMPORT-002 · Code imported directly from a remote URL
remote-import · critical severity · high confidence · block
This rule identifies remote import behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
IMPORT-003 · Node.js internal or global require bypass
dynamic-import · high severity · high confidence · review
This rule identifies dynamic import behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: code · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx · Context downgrade: allowed
INSTALL-001 · Setup script installs host packages or global developer tools
system-installation · medium severity · high confidence · review
This rule identifies system installation behavior that can affect repository trust or execution safety.
Legitimate use: Bootstrap scripts commonly install reviewed packages and developer tools.
Review action: Review package names, sources, versions, and privileges before running the installer.
Scope: raw · Paths: install.*, setup.*, bootstrap.*, provision.*, *.sh, *.bash, *.zsh, *.fish, *.ps1, *.bat, *.cmd · Context downgrade: allowed
IOC-HASH-SHA256 · File hash matches confirmed intelligence
known-malicious-file · critical severity · high confidence · block
This rule identifies known malicious file behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Isolate the file and follow incident-response procedures.
Scope: structured · Paths: ** · Context downgrade: disabled
IOC-PKG-* · Package declaration matches confirmed intelligence
known-malicious-package · critical severity · high confidence · block
This rule identifies known malicious package behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the advisory and resolved package before installation.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: disabled
IPURL-001 · URL uses a hardcoded public-looking IP address
hardcoded-network · medium severity · medium confidence · review
This rule identifies hardcoded network behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: ** · Context downgrade: allowed
JVM-001 · JVM build configuration invokes an external process
jvm-build-execution · high severity · medium confidence · review
This rule identifies jvm build execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: build.gradle, build.gradle.kts, pom.xml, settings.gradle, settings.gradle.kts · Context downgrade: allowed
JVM-002 · JVM build uses a custom dependency repository
jvm-repository · medium severity · medium confidence · review
This rule identifies jvm repository behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: build.gradle, build.gradle.kts, pom.xml, settings.gradle, settings.gradle.kts · Context downgrade: allowed
JVMWRAP-001 · JVM wrapper distribution URL is missing or redirects from the official source
jvm-wrapper-source · high severity · high confidence · review
This rule identifies jvm wrapper source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the wrapper distribution before running it.
Scope: structured · Paths: ** · Context downgrade: allowed
JVMWRAP-002 · JVM wrapper distribution has no expected SHA-256
jvm-wrapper-integrity · medium severity · high confidence · harden
This rule identifies jvm wrapper integrity behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Pin the reviewed distribution SHA-256 in the wrapper properties.
Scope: structured · Paths: ** · Context downgrade: allowed
JVMWRAP-003 · JVM wrapper distribution SHA-256 is malformed
jvm-wrapper-integrity · high severity · high confidence · review
This rule identifies jvm wrapper integrity behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Replace the checksum with the reviewed 64-character SHA-256.
Scope: structured · Paths: ** · Context downgrade: allowed
LOCK-001 · Lockfile resolves a package from a nonstandard URL
lockfile-tampering · high severity · medium confidence · review
This rule identifies lockfile tampering behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: package-lock.json, npm-shrinkwrap.json, yarn.lock, pnpm-lock.yaml, Pipfile.lock, poetry.lock, Gemfile.lock · Context downgrade: allowed
MINER-001 · Cryptocurrency mining indicator
cryptomining · high severity · high confidence · review
This rule identifies cryptomining behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
NET-001 · Remote content fetch
remote-fetch · medium severity · low confidence · informational
This rule identifies remote fetch behavior that can affect repository trust or execution safety.
Legitimate use: Installers and update tools may retrieve content from reviewed, pinned sources.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: ** · Context downgrade: allowed
NET-002 · Known exfiltration or tunneling service endpoint
suspicious-network · high severity · high confidence · review
This rule identifies suspicious network behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
NPMRC-001 · Package manager configuration contains a registry credential
package-registry · high severity · high confidence · review
This rule identifies package registry behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: .npmrc, .yarnrc, .yarnrc.yml · Context downgrade: allowed
NPMRC-002 · Custom package registry
package-registry · medium severity · medium confidence · review
This rule identifies package registry behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: .npmrc, .yarnrc, .yarnrc.yml · Context downgrade: allowed
NUGET-001 · NuGet configuration uses an alternate package source
nuget-package-source · medium severity · medium confidence · review
This rule identifies nuget package source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the feed and constrain package source mapping.
Scope: structured · Paths: ** · Context downgrade: allowed
OBFS-001 · Long base64-like payload
encoded-payload · medium severity · medium confidence · review
This rule identifies encoded payload behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: ** · Context downgrade: allowed
OBFS-002 · String decoding or character-code construction
string-obfuscation · medium severity · medium confidence · review
This rule identifies string obfuscation behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: ** · Context downgrade: allowed
OBFS-003 · Dense hexadecimal or Unicode escape sequence
string-obfuscation · medium severity · low confidence · informational
This rule identifies string obfuscation behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: ** · Context downgrade: allowed
OBFS-004 · Very long single line
minified-or-obfuscated · low severity · low confidence · informational
This rule identifies minified or obfuscated behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review generated or minified content and its provenance.
Scope: structured · Paths: ** · Context downgrade: allowed
OBFS-005 · High-entropy content appears beside execution
high-entropy-code · medium severity · medium confidence · review
This rule identifies high entropy code behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Decode and inspect the content in an isolated environment.
Scope: structured · Paths: ** · Context downgrade: allowed
OBFS-006 · Runtime string reversal or computed global access
string-obfuscation · medium severity · medium confidence · review
This rule identifies string obfuscation behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx · Context downgrade: allowed
OBFS-007 · Character shuffler associated with generated obfuscators
string-obfuscation · medium severity · medium confidence · review
This rule identifies string obfuscation behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx · Context downgrade: allowed
OBFS-008 · Constructor or prototype access can bypass direct-call signatures
prototype-evasion · medium severity · low confidence · informational
This rule identifies prototype evasion behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: *.js, *.cjs, *.mjs, *.jsx, *.ts, *.tsx · Context downgrade: allowed
OBFS-009 · Exported router accesses Node global state
global-access · medium severity · low confidence · informational
This rule identifies global access behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: *.js, *.cjs · Context downgrade: allowed
PATH-001 · Request-controlled path reaches a file operation
path-traversal · medium severity · medium confidence · review
This rule identifies path traversal behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: code · Paths: ** · Context downgrade: allowed
PERSIST-001 · Command creates a service, daemon, login item, or WMI event subscription
system-persistence · critical severity · high confidence · block
This rule identifies system persistence behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
PERSIST-002 · Repository contains an automatically started service, timer, or launchd job
startup-configuration · medium severity · high confidence · review
This rule identifies startup configuration behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the executable, arguments, user, privileges, and activation conditions before installing or enabling this startup configuration.
Scope: raw · Paths: *.service, *.timer, *.plist · Context downgrade: allowed
PHP-001 · Composer package defines an installation or update script
composer-script · high severity · medium confidence · review
This rule identifies composer script behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: composer.json · Context downgrade: allowed
PHP-002 · Composer defines alternate package repositories
composer-package-source · medium severity · medium confidence · review
This rule identifies composer package source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review repository precedence and the resolved composer.lock.
Scope: structured · Paths: ** · Context downgrade: allowed
PHP-003 · Composer permits every dependency plugin to execute
composer-plugin-execution · high severity · high confidence · review
This rule identifies composer plugin execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Replace wildcard permission with explicit reviewed plugin names.
Scope: structured · Paths: ** · Context downgrade: allowed
PKG-001 · Package lifecycle script is present
package-lifecycle · medium severity · medium confidence · review
This rule identifies package lifecycle behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the script before installing dependencies.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PKG-002 · Dependency uses a non-registry source
suspicious-dependency-source · high severity · medium confidence · review
This rule identifies suspicious dependency source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify and pin the dependency source.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PKG-003 · Dependency uses a placeholder-like version
suspicious-dependency-version · medium severity · medium confidence · review
This rule identifies suspicious dependency version behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the package name and version.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PKG-004 · Package exposes an executable command
package-binary · low severity · medium confidence · informational
This rule identifies package binary behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the executable before installing globally.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PKG-005 · Dependency uses an unusually high major version
dependency-confusion · medium severity · medium confidence · review
This rule identifies dependency confusion behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify registry ownership and the resolved artifact.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PKG-006 · Package binary target escapes the package or embeds execution
package-binary · high severity · high confidence · review
This rule identifies package binary behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Constrain the target to a reviewed local file.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PKG-007 · Package script downloads and executes content
package-script · high severity · medium confidence · review
This rule identifies package script behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the script before running package-manager commands.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PKG-008 · Dependency override changes package source or identity
dependency-override · high severity · medium confidence · review
This rule identifies dependency override behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the override and pin it to a trusted immutable artifact.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PKG-009 · Dependency name resolves to a different registry package
package-alias · medium severity · medium confidence · review
This rule identifies package alias behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the alias target, publisher, and resolved artifact.
Scope: structured · Paths: package.json and supported dependency manifests · Context downgrade: allowed
PROTO-001 · Write to JavaScript prototype internals
prototype-pollution · high severity · medium confidence · review
This rule identifies prototype pollution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: code · Paths: *.js, *.cjs, *.mjs, *.ts, *.tsx, *.jsx · Context downgrade: allowed
PY-001 · Python package defines installation-time command hooks
python-install-hook · high severity · medium confidence · review
This rule identifies python install hook behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: setup.py, setup.cfg, pyproject.toml · Context downgrade: allowed
PY-002 · Python dependency is loaded from a URL or VCS source
python-dependency-source · high severity · medium confidence · review
This rule identifies python dependency source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: requirements*.txt, pyproject.toml, Pipfile, setup.py, setup.cfg · Context downgrade: allowed
PY-003 · pip configuration changes package lookup sources
python-package-source · medium severity · medium confidence · review
This rule identifies python package source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the source and avoid mixing public and private indexes for the same package names.
Scope: structured · Paths: ** · Context downgrade: allowed
PY-004 · Python .pth file contains a startup import line
python-startup-hook · medium severity · high confidence · review
This rule identifies python startup hook behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the import and its source before installation in a Python site directory, where it runs at startup. Benign packages also use this mechanism.
Scope: raw · Paths: *.pth · Context downgrade: allowed
PY-005 · Python startup customization module contains content
python-startup-hook · medium severity · high confidence · review
This rule identifies python startup hook behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the module before placing it on Python's search path, where it can be imported at startup. Legitimate environment customization also uses these modules.
Scope: raw · Paths: sitecustomize.py, usercustomize.py · Context downgrade: allowed
REPO-001 · Repository has no top-level README
repository-hygiene · low severity · high confidence · harden
This rule identifies repository hygiene behavior that can affect repository trust or execution safety.
Legitimate use: Private or early-stage repositories may intentionally omit public documentation.
Review action: Ask the owner for setup and provenance documentation.
Scope: structured · Paths: repository root · Context downgrade: allowed
REPO-002 · Repository has no top-level license
repository-hygiene · low severity · high confidence · harden
This rule identifies repository hygiene behavior that can affect repository trust or execution safety.
Legitimate use: Private or early-stage repositories may intentionally omit public documentation.
Review action: Clarify the code origin and permitted use.
Scope: structured · Paths: repository root · Context downgrade: allowed
REVSHELL-001 · Reverse or bind shell behavior
reverse-shell · critical severity · high confidence · block
This rule identifies reverse shell behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
REVSHELL-002 · Language one-liner creates a command shell over a socket
reverse-shell · critical severity · high confidence · block
This rule identifies reverse shell behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
RUBY-001 · Ruby dependency is loaded from a Git or path source
ruby-dependency-source · high severity · medium confidence · review
This rule identifies ruby dependency source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: Gemfile, *.gemspec · Context downgrade: allowed
RUBY-002 · Bundler package source is redirected
ruby-package-source · medium severity · medium confidence · review
This rule identifies ruby package source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the gem source or mirror and review Gemfile.lock.
Scope: structured · Paths: ** · Context downgrade: allowed
RUST-001 · Rust package declares a build script
rust-build-script · medium severity · high confidence · review
This rule identifies rust build script behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect build.rs or the referenced build script before compiling.
Scope: raw · Paths: Cargo.toml · Context downgrade: allowed
RUST-002 · Cargo automatically executes a package build.rs
rust-build-script · medium severity · high confidence · review
This rule identifies rust build script behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect build.rs and its build dependencies before compiling.
Scope: structured · Paths: ** · Context downgrade: allowed
RUST-003 · Cargo configuration redirects dependency resolution
rust-registry-redirection · high severity · high confidence · review
This rule identifies rust registry redirection behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the registry or source replacement before fetching dependencies.
Scope: structured · Paths: ** · Context downgrade: allowed
RUST-004 · Cargo dependency source override
rust-dependency-override · high severity · medium confidence · review
This rule identifies rust dependency override behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify and pin the replacement dependency source.
Scope: structured · Paths: ** · Context downgrade: allowed
RUST-005 · Cargo dependency uses a non-default source
rust-dependency-source · high severity · medium confidence · review
This rule identifies rust dependency source behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify the dependency source and pin remote revisions.
Scope: structured · Paths: ** · Context downgrade: allowed
SECRET-001 · Private key material
secret · high severity · high confidence · review
This rule identifies secret behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Revoke or rotate the credential and remove it from repository history.
Scope: raw · Paths: ** · Context downgrade: disabled
SECRET-002 · Provider credential pattern
secret · high severity · high confidence · review
This rule identifies secret behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Revoke or rotate the credential and remove it from repository history.
Scope: raw · Paths: ** · Context downgrade: disabled
SECRET-003 · Generic API key, access token, or client secret assignment
secret · high severity · medium confidence · review
This rule identifies secret behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Verify whether this is a real credential; if so, revoke it and remove it from repository history.
Scope: raw · Paths: ** · Context downgrade: disabled
SHELL-001 · Shell profile or operating-system startup persistence
shell-persistence · high severity · medium confidence · review
This rule identifies shell persistence behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not run the repository. Verify the source and intent in an isolated environment.
Scope: raw · Paths: ** · Context downgrade: allowed
SOCIAL-001 · Instructions pressure the reader to bypass security controls
social-engineering · medium severity · medium confidence · review
This rule identifies social engineering behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Do not follow the instruction until the repository and sender are independently verified.
Scope: raw · Paths: README*, *.md, *.txt, *.rst, *.adoc · Context downgrade: allowed
SOCIAL-002 · Interview instructions combine urgency with execution pressure
social-engineering · low severity · medium confidence · informational
This rule identifies social engineering behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Independently verify the sender and repository; urgency should not override safe review.
Scope: raw · Paths: README*, *.md, *.txt, *.rst, *.adoc · Context downgrade: allowed
SYMLINK-001 · Symbolic link escapes the repository
escaping-symlink · high severity · high confidence · review
This rule identifies escaping symlink behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Remove or replace the escaping link.
Scope: structured · Paths: ** · Context downgrade: allowed
SYMLINK-002 · Symbolic link target is unavailable
broken-symlink · medium severity · medium confidence · review
This rule identifies broken symlink behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Review the link target and packaging.
Scope: structured · Paths: ** · Context downgrade: allowed
TYPOSQUAT-001 · Dependency resembles a commonly targeted package name
typosquatting · high severity · medium confidence · review
This rule identifies typosquatting behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: package.json, requirements*.txt, pyproject.toml, Pipfile, Gemfile · Context downgrade: allowed
UNICODE-001 · Invisible or bidirectional Unicode control character
unicode-obfuscation · high severity · medium confidence · review
This rule identifies unicode obfuscation behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: raw · Paths: ** · Context downgrade: allowed
UNSERIALIZE-001 · Unsafe deserialization primitive
unsafe-deserialization · high severity · medium confidence · review
This rule identifies unsafe deserialization behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the surrounding code and remove the behavior if it is not essential.
Scope: code · Paths: ** · Context downgrade: allowed
YARN-001 · Project selects a local Yarn executable
package-manager-execution · medium severity · high confidence · review
This rule identifies package manager execution behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the referenced Yarn executable before running yarn commands.
Scope: structured · Paths: ** · Context downgrade: allowed
YARN-002 · Project loads a Yarn plugin
package-manager-plugin · medium severity · high confidence · review
This rule identifies package manager plugin behavior that can affect repository trust or execution safety.
Legitimate use: The behavior may be legitimate when its inputs, destination, and execution context are understood.
Review action: Inspect the plugin source before running yarn commands.
Scope: structured · Paths: ** · Context downgrade: allowed