tally-cli 0.1.0

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,535 @@
+# tally
+
+[![codecov](https://codecov.io/gh/tinovyatkin/tally/graph/badge.svg?token=J3vK0hyLkf)](https://codecov.io/gh/tinovyatkin/tally)
+
+tally keeps Dockerfiles and Containerfiles clean, modern, and consistent — using BuildKit's own parser and checks (the same foundation behind
+`docker buildx`) plus safe auto-fixes. It runs fast, doesn't require Docker Desktop or a daemon, and fits neatly into CI. If that sounds like your
+workflow, try `tally check .`.
+
+```bash
+# Lint everything in the repo (recursive)
+tally check .
+
+# Apply all safe fixes automatically
+tally check --fix Dockerfile
+```
+
+## Why tally?
+
+Dockerfile linting usually means picking a compromise:
+
+- **Hadolint** is popular and battle-tested, but it uses its own Dockerfile parser, so support for newer BuildKit features can lag behind. It also
+  is commonly consumed as a prebuilt binary, and it focuses on reporting — not fixing.
+- **`docker buildx --check`** runs Docker's official BuildKit checks, but it requires the Docker/buildx toolchain and can be heavier than a pure
+  static linter (and not always available if you're using Podman/Finch/other runtimes).
+
+tally exists to bring modern linter ergonomics to container builds:
+
+- **BuildKit-native parsing**: understands modern syntax like heredocs, `RUN --mount=...`, and `ADD --checksum=...`.
+- **Fixes, not just findings**: applies safe, mechanical fixes automatically (`--fix`), with per-rule control when you need it.
+- **Easy to install anywhere**: available via Homebrew, Go, npm, pip, and RubyGems — so it can flow through your existing artifact mirrors.
+- **Container ecosystem friendly**: supports Dockerfile/Containerfile conventions and `.dockerignore`/`.containerignore`.
+- **A growing ruleset**: combines official BuildKit checks, Hadolint-compatible rules, and tally-specific rules.
+
+Roadmap: editor integrations (VS Code, Zed), more auto-fixes, and higher-level rules (cache & tmpfs mount recommendations, tooling-aware checks for
+uv/bun, line-length and layer optimizations).
+
+## Supported Rules
+
+tally integrates rules from multiple sources:
+
+<!-- BEGIN RULES_TABLE -->
+
+| Source                                                          | Rules    | Description                                                                                   |
+| --------------------------------------------------------------- | -------- | --------------------------------------------------------------------------------------------- |
+| **[BuildKit](https://docs.docker.com/reference/build-checks/)** | 22 rules | Docker's official Dockerfile checks (automatically captured)                                  |
+| **tally**                                                       | 3 rules  | Custom rules including secret detection with [gitleaks](https://github.com/gitleaks/gitleaks) |
+| **[Hadolint](https://github.com/hadolint/hadolint)**            | 22 rules | Hadolint-compatible Dockerfile rules (expanding)                                              |
+
+<!-- END RULES_TABLE -->
+
+**See [RULES.md](RULES.md) for the complete rules reference.**
+
+## Installation
+
+### Homebrew (macOS/Linux)
+
+```bash
+brew install tinovyatkin/tap/tally
+```
+
+### NPM
+
+```bash
+npm install -g tally-cli
+```
+
+### PyPI
+
+```bash
+pip install tally-cli
+```
+
+### RubyGems
+
+```bash
+gem install tally-cli
+```
+
+### Go
+
+```bash
+go install github.com/tinovyatkin/tally@latest
+```
+
+### From Source
+
+```bash
+git clone https://github.com/tinovyatkin/tally.git
+cd tally
+go build .
+```
+
+## Usage
+
+```bash
+# Check a Dockerfile
+tally check Dockerfile
+
+# Check all Dockerfiles in current directory (recursive)
+tally check .
+
+# Check with glob patterns
+tally check "**/*.Dockerfile"
+
+# Exclude patterns
+tally check --exclude "vendor/*" --exclude "test/*" .
+
+# Check with max lines limit
+tally check --max-lines 100 Dockerfile
+
+# Output as JSON
+tally check --format json Dockerfile
+
+# Check multiple files
+tally check Dockerfile.dev Dockerfile.prod
+
+# Enable context-aware rules (e.g., copy-ignored-file)
+tally check --context . Dockerfile
+```
+
+### File Discovery
+
+When given a directory, tally recursively searches for Dockerfiles using these default patterns:
+
+- `Dockerfile`
+- `Dockerfile.*` (e.g., `Dockerfile.dev`, `Dockerfile.prod`)
+- `*.Dockerfile` (e.g., `api.Dockerfile`, `frontend.Dockerfile`)
+- `Containerfile` (Podman convention)
+- `Containerfile.*`
+- `*.Containerfile`
+
+Use `--exclude` to filter out unwanted files:
+
+```bash
+# Exclude vendor and test directories
+tally check --exclude "vendor/*" --exclude "test/*" .
+
+# Exclude all .bak files
+tally check --exclude "*.bak" .
+```
+
+## Rules Overview
+
+For the complete list of all supported rules, see **[RULES.md](RULES.md)**.
+
+### Context-Aware Rules
+
+Some rules require build context awareness. Enable them with the `--context` flag:
+
+```bash
+# Enable context-aware rules
+tally check --context . Dockerfile
+```
+
+**copy-ignored-file**: Detects when `COPY` or `ADD` commands reference files that would be excluded by `.dockerignore`. This helps catch mistakes
+where files are copied but won't actually be included in the build.
+
+```dockerfile
+# .dockerignore contains: *.log
+
+# This will trigger a warning:
+COPY app.log /app/  # File matches .dockerignore pattern
+
+# Heredoc sources are exempt (they're inline, not from context):
+COPY <<EOF /app/config.txt
+inline content
+EOF
+```
+
+## Ignoring Violations
+
+You can suppress specific violations using inline comment directives.
+
+### Next-Line Directives
+
+Suppress violations on the next line:
+
+```dockerfile
+# tally ignore=StageNameCasing
+FROM alpine AS Build
+```
+
+### Global Directives
+
+Suppress violations throughout the entire file:
+
+```dockerfile
+# tally global ignore=max-lines
+FROM alpine
+# ... rest of file is not checked for max-lines
+```
+
+### Multiple Rules
+
+Suppress multiple rules with comma-separated values:
+
+```dockerfile
+# tally ignore=StageNameCasing,DL3006
+FROM Ubuntu AS Build
+```
+
+### Adding Reasons
+
+Document why a rule is being ignored using `;reason=` (BuildKit-style separator):
+
+```dockerfile
+# tally ignore=DL3006;reason=Using older base image for compatibility
+FROM ubuntu:16.04
+
+# tally global ignore=max-lines;reason=Generated file, size is expected
+FROM alpine
+
+# check=skip=StageNameCasing;reason=Legacy naming convention
+FROM alpine AS Build
+```
+
+Use `--require-reason` to enforce that all ignore directives include an explanation:
+
+```bash
+tally check --require-reason Dockerfile
+```
+
+Note: The `;reason=` syntax is a tally extension that works with all directive formats. BuildKit silently ignores the `reason` option.
+
+### Migration Compatibility
+
+tally supports directive formats from other linters for easy migration:
+
+```dockerfile
+# hadolint ignore=DL3006
+FROM ubuntu
+
+# hadolint global ignore=DL3008
+FROM alpine
+
+# check=skip=StageNameCasing
+FROM alpine AS Build
+```
+
+### Suppressing All Rules
+
+Use `all` to suppress all rules on a line:
+
+```dockerfile
+# tally ignore=all
+FROM Ubuntu AS Build
+```
+
+### CLI Options
+
+| Flag                       | Description                                                |
+| -------------------------- | ---------------------------------------------------------- |
+| `--no-inline-directives`   | Disable processing of inline ignore directives             |
+| `--warn-unused-directives` | Warn about directives that don't suppress any violations   |
+| `--require-reason`         | Warn about ignore directives without `reason=` explanation |
+
+### Configuration
+
+Inline directive behavior can be configured in `.tally.toml`:
+
+```toml
+[inline-directives]
+enabled = true        # Process inline directives (default: true)
+warn-unused = false   # Warn about unused directives (default: false)
+validate-rules = false # Warn about unknown rule codes (default: false)
+require-reason = false # Require reason= on all ignore directives (default: false)
+```
+
+## Configuration
+
+tally supports configuration via TOML config files, environment variables, and CLI flags.
+
+### Config File
+
+Create a `.tally.toml` or `tally.toml` file in your project:
+
+```toml
+[output]
+format = "text"          # text, json, sarif, github-actions, markdown
+path = "stdout"          # stdout, stderr, or file path
+show-source = true       # Show source code snippets
+fail-level = "style"     # Minimum severity for exit code 1
+
+# Rule selection (Ruff-style)
+[rules]
+include = ["buildkit/*", "tally/*"]           # Enable rules by namespace or specific rule
+exclude = ["buildkit/MaintainerDeprecated"]   # Disable specific rules
+
+# Per-rule configuration (severity, options)
+[rules.tally.max-lines]
+severity = "error"
+max = 500
+skip-blank-lines = true
+skip-comments = true
+
+[rules.buildkit.StageNameCasing]
+severity = "info"         # Downgrade severity
+
+[rules.hadolint.DL3026]
+severity = "warning"
+trusted-registries = ["docker.io", "gcr.io"]
+```
+
+### Config File Discovery
+
+tally uses cascading config discovery similar to [Ruff](https://docs.astral.sh/ruff/configuration/):
+
+1. Starting from the Dockerfile's directory, walks up the filesystem
+2. Stops at the first `.tally.toml` or `tally.toml` found
+3. Uses that config (no merging with parent configs)
+
+This allows monorepo setups with per-directory configurations.
+
+### Priority Order
+
+Configuration sources are applied in this order (highest priority first):
+
+1. **CLI flags** (`--max-lines 100`)
+2. **Environment variables** (`TALLY_RULES_MAX_LINES_MAX=100`)
+3. **Config file** (`.tally.toml` or `tally.toml`)
+4. **Built-in defaults**
+
+### Environment Variables
+
+| Variable                                 | Description                                                           |
+| ---------------------------------------- | --------------------------------------------------------------------- |
+| `TALLY_OUTPUT_FORMAT`                    | Output format (`text`, `json`, `sarif`, `github-actions`, `markdown`) |
+| `TALLY_OUTPUT_PATH`                      | Output destination (`stdout`, `stderr`, or file path)                 |
+| `TALLY_OUTPUT_SHOW_SOURCE`               | Show source snippets (`true`/`false`)                                 |
+| `TALLY_OUTPUT_FAIL_LEVEL`                | Minimum severity for non-zero exit                                    |
+| `NO_COLOR`                               | Disable colored output (standard env var)                             |
+| `TALLY_EXCLUDE`                          | Glob pattern(s) to exclude files (comma-separated)                    |
+| `TALLY_CONTEXT`                          | Build context directory for context-aware rules                       |
+| `TALLY_RULES_MAX_LINES_MAX`              | Maximum lines allowed                                                 |
+| `TALLY_RULES_MAX_LINES_SKIP_BLANK_LINES` | Exclude blank lines (`true`/`false`)                                  |
+| `TALLY_RULES_MAX_LINES_SKIP_COMMENTS`    | Exclude comments (`true`/`false`)                                     |
+| `TALLY_NO_INLINE_DIRECTIVES`             | Disable inline directive processing (`true`/`false`)                  |
+| `TALLY_INLINE_DIRECTIVES_WARN_UNUSED`    | Warn about unused directives (`true`/`false`)                         |
+| `TALLY_INLINE_DIRECTIVES_REQUIRE_REASON` | Require reason= on ignore directives (`true`/`false`)                 |
+
+### CLI Flags
+
+```bash
+# Specify config file explicitly
+tally check --config /path/to/.tally.toml Dockerfile
+
+# Override max-lines from config
+tally check --max-lines 200 Dockerfile
+
+# Exclude blank lines and comments from count
+tally check --max-lines 100 --skip-blank-lines --skip-comments Dockerfile
+```
+
+## Output Formats
+
+tally supports multiple output formats for different use cases.
+
+### Text (default)
+
+Human-readable output with colors and source code snippets:
+
+```bash
+tally check Dockerfile
+```
+
+```text
+WARNING: StageNameCasing - https://docs.docker.com/go/dockerfile/rule/stage-name-casing/
+Stage name 'Builder' should be lowercase
+
+Dockerfile:2
+────────────────────
+   1 │ FROM alpine
+>>>2 │ FROM ubuntu AS Builder
+   3 │ RUN echo "hello"
+────────────────────
+```
+
+### JSON
+
+Machine-readable format with summary statistics and scan metadata:
+
+```bash
+tally check --format json Dockerfile
+```
+
+The JSON output includes:
+
+- `files`: Array of files with their violations
+- `summary`: Aggregate statistics (total, errors, warnings, etc.)
+- `files_scanned`: Total number of files scanned
+- `rules_enabled`: Number of active rules (with `DefaultSeverity != "off"`)
+
+```json
+{
+  "files": [
+    {
+      "file": "Dockerfile",
+      "violations": [
+        {
+          "location": {
+            "file": "Dockerfile",
+            "start": { "line": 2, "column": 0 }
+          },
+          "rule": "buildkit/StageNameCasing",
+          "message": "Stage name 'Builder' should be lowercase",
+          "severity": "warning",
+          "docUrl": "https://docs.docker.com/go/dockerfile/rule/stage-name-casing/"
+        }
+      ]
+    }
+  ],
+  "summary": {
+    "total": 1,
+    "errors": 0,
+    "warnings": 1,
+    "info": 0,
+    "style": 0,
+    "files": 1
+  },
+  "files_scanned": 1,
+  "rules_enabled": 35
+}
+```
+
+### SARIF
+
+[Static Analysis Results Interchange Format](https://docs.oasis-open.org/sarif/sarif/v2.1.0/) for CI/CD integration with GitHub Code Scanning, Azure DevOps, and other tools:
+
+```bash
+tally check --format sarif Dockerfile > results.sarif
+```
+
+### GitHub Actions
+
+Native GitHub Actions workflow command format for inline annotations:
+
+```bash
+tally check --format github-actions Dockerfile
+```
+
+```text
+::warning file=Dockerfile,line=2,title=StageNameCasing::Stage name 'Builder' should be lowercase
+```
+
+### Markdown
+
+Concise Markdown tables optimized for AI agents and token efficiency:
+
+```bash
+tally check --format markdown Dockerfile
+```
+
+```markdown
+**2 issues** in `Dockerfile`
+
+| Line | Issue                                       |
+| ---- | ------------------------------------------- |
+| 10   | ❌ Use absolute WORKDIR                     |
+| 2    | ⚠️ Stage name 'Builder' should be lowercase |
+```
+
+Features:
+
+- Summary upfront with issue counts
+- Sorted by severity (errors first)
+- Emoji indicators: ❌ error, ⚠️ warning, ℹ️ info, 💅 style
+- No rule codes or doc URLs (token-efficient)
+- Multi-file support with File column when needed
+
+### Output Options
+
+| Flag            | Description                                                          |
+| --------------- | -------------------------------------------------------------------- |
+| `--format, -f`  | Output format: `text`, `json`, `sarif`, `github-actions`, `markdown` |
+| `--output, -o`  | Output destination: `stdout`, `stderr`, or file path                 |
+| `--no-color`    | Disable colored output (also respects `NO_COLOR` env var)            |
+| `--show-source` | Show source code snippets (default: true)                            |
+| `--hide-source` | Hide source code snippets                                            |
+
+### Exit Codes
+
+| Code | Meaning                                           |
+| ---- | ------------------------------------------------- |
+| `0`  | No violations (or below `--fail-level` threshold) |
+| `1`  | Violations found at or above `--fail-level`       |
+| `2`  | Parse or configuration error                      |
+
+### Fail Level
+
+Control which severity levels cause a non-zero exit code:
+
+```bash
+# Fail only on errors (ignore warnings)
+tally check --fail-level error Dockerfile
+
+# Never fail (useful for CI reporting without blocking)
+tally check --fail-level none --format sarif Dockerfile > results.sarif
+
+# Fail on any violation including style issues (default behavior)
+tally check --fail-level style Dockerfile
+```
+
+Available levels (from most to least severe): `error`, `warning`, `info`, `style` (default), `none`
+
+## Development
+
+### Running Tests
+
+```bash
+# Run all tests
+make test
+
+# Run linting
+make lint
+
+# Run copy/paste detection (CPD)
+make cpd
+```
+
+### Code Quality
+
+This project uses:
+
+- **golangci-lint** for Go linting
+- **PMD CPD** for copy/paste detection (minimum 100 tokens)
+
+Copy/paste detection runs automatically in CI and helps identify duplicate code patterns.
+
+## Contributing
+
+See [CLAUDE.md](CLAUDE.md) for development guidelines.
+
+## License
+
+Apache-2.0

package/bin/index.js

@@ -0,0 +1,22 @@
+#!/usr/bin/env node
+
+const { spawn } = require('child_process');
+const { getExePath } = require('../get-exe');
+
+const command_args = process.argv.slice(2);
+
+const child = spawn(
+    getExePath(),
+    command_args,
+    { stdio: "inherit" });
+
+child.on('error', function (err) {
+    console.error(`Failed to execute binary: ${err.message}`);
+    process.exit(1);
+});
+
+child.on('close', function (code) {
+    if (code !== 0) {
+        process.exit(code);
+    }
+});

package/get-exe.js

@@ -0,0 +1,18 @@
+function getExePath() {
+  // Detect OS
+  // https://nodejs.org/api/process.html#process_process_platform
+  let os = process.platform;
+  let extension = "";
+  if (["win32", "cygwin"].includes(process.platform)) {
+    os = "windows";
+    extension = ".exe";
+  }
+
+  // Detect architecture
+  // https://nodejs.org/api/process.html#process_process_arch
+  let arch = process.arch;
+
+  return require.resolve(`@contino/tally-${os}-${arch}/bin/tally${extension}`);
+}
+
+exports.getExePath = getExePath;

package/package.json

@@ -0,0 +1,43 @@
+{
+  "name": "tally-cli",
+  "version": "0.1.0",
+  "description": "A fast, configurable linter for Dockerfiles and Containerfiles",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/tinovyatkin/tally.git"
+  },
+  "main": "bin/index.js",
+  "files": [
+    "postinstall.js",
+    "get-exe.js"
+  ],
+  "bin": {
+    "tally": "bin/index.js"
+  },
+  "keywords": [
+    "docker",
+    "dockerfile",
+    "containerfile",
+    "linter",
+    "lint",
+    "container"
+  ],
+  "author": "tinovyatkin",
+  "license": "Apache-2.0",
+  "bugs": {
+    "url": "https://github.com/tinovyatkin/tally/issues"
+  },
+  "homepage": "https://github.com/tinovyatkin/tally#readme",
+  "optionalDependencies": {
+    "@contino/tally-darwin-arm64": "0.1.0",
+    "@contino/tally-darwin-x64": "0.1.0",
+    "@contino/tally-linux-arm64": "0.1.0",
+    "@contino/tally-linux-x64": "0.1.0",
+    "@contino/tally-windows-arm64": "0.1.0",
+    "@contino/tally-windows-x64": "0.1.0",
+    "@contino/tally-freebsd-x64": "0.1.0"
+  },
+  "scripts": {
+    "postinstall": "node postinstall.js"
+  }
+}

package/postinstall.js

@@ -0,0 +1,4 @@
+#!/usr/bin/env node
+
+// This file is intentionally empty to prevent postinstall errors
+// when optional dependencies are not installed