falsegreen 0.1.0__tar.gz

falsegreen-0.1.0/.claude-plugin/marketplace.json

@@ -0,0 +1,20 @@
+{
+  "name": "falsegreen",
+  "owner": {
+    "name": "Vinicius Queiroz",
+    "url": "https://github.com/vinicq"
+  },
+  "metadata": {
+    "description": "Find unit tests that give false positives. Deterministic scanner plus a semantic pass that checks the expected value against intended behavior.",
+    "version": "0.1.0"
+  },
+  "plugins": [
+    {
+      "name": "falsegreen",
+      "source": "./",
+      "category": "testing",
+      "keywords": ["testing", "pytest", "test-quality", "false-positive", "code-review"],
+      "description": "Audit unit tests for false positives: green tests that protect nothing, and tests that pass while asserting the wrong expected value."
+    }
+  ]
+}

falsegreen-0.1.0/.claude-plugin/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "falsegreen",
+  "version": "0.1.0",
+  "description": "Audit unit tests for false positives. Judges the test's expected value against intended behavior (spec/contract), not just what the code returns.",
+  "author": { "name": "Vinicius Queiroz", "url": "https://github.com/vinicq" },
+  "homepage": "https://github.com/vinicq/falsegreen",
+  "repository": { "url": "https://github.com/vinicq/falsegreen" },
+  "license": "MIT",
+  "keywords": ["testing", "pytest", "test-quality", "false-positive", "code-review"],
+  "skills": ["./skills/falsegreen"]
+}

falsegreen-0.1.0/.gitattributes

@@ -0,0 +1,3 @@
+* text=auto eol=lf
+*.png binary
+*.jpg binary

falsegreen-0.1.0/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @vinicq

falsegreen-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,37 @@
+---
+name: Bug report
+about: A wrong result from falsegreen (false positive, false negative, or a crash)
+title: ""
+labels: bug
+assignees: ""
+---
+
+## What happened
+
+<!-- For a FALSE POSITIVE: paste the smallest test snippet that got wrongly
+flagged, and the code falsegreen emitted (e.g. C13). -->
+<!-- For a FALSE NEGATIVE: paste the bad test that slipped through. -->
+
+```python
+# minimal test snippet
+```
+
+## What falsegreen reported
+
+<!-- The exact output, including the case code(s). Paste `falsegreen <file>`
+output or the relevant line. -->
+
+## What you expected
+
+<!-- Flagged or not flagged, and why. For a false positive, why the snippet is
+a legitimate test. -->
+
+## Environment
+
+- falsegreen version (or commit SHA):
+- Python version:
+- OS:
+
+## Anything else
+
+<!-- pytest plugins in play (pytest-mock, hypothesis), unittest vs pytest style, etc. -->

falsegreen-0.1.0/.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security report
+    url: https://github.com/vinicq/falsegreen/security/advisories/new
+    about: Report a vulnerability privately. Do not open a public issue.
+  - name: Question or idea
+    url: https://github.com/vinicq/falsegreen/discussions
+    about: Open-ended questions and discussion.

falsegreen-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,27 @@
+---
+name: Feature request
+about: A new detection rule, a config option, or another improvement
+title: ""
+labels: enhancement
+assignees: ""
+---
+
+## The problem
+
+<!-- What kind of false-positive test is escaping today, or what friction you hit. -->
+
+## Proposed rule or change
+
+<!-- For a NEW detection rule: show the bad pattern it should catch, and a
+legitimate look-alike it must NOT catch. State whether it should block (HIGH) or
+only warn (LOW). Remember: HIGH must almost never fire on legitimate tests. -->
+
+```python
+# bad pattern (should be flagged)
+
+# legitimate look-alike (must stay clean)
+```
+
+## Alternatives considered
+
+<!-- Existing tools (ruff PT rules, PyNose, mutmut) that already cover this? -->

falsegreen-0.1.0/.github/dependabot.yml

@@ -0,0 +1,24 @@
+version: 2
+updates:
+  - package-ecosystem: pip
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+    open-pull-requests-limit: 5
+    labels:
+      - dependencies
+    commit-message:
+      prefix: "chore(deps)"
+
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly
+      day: monday
+    open-pull-requests-limit: 3
+    labels:
+      - dependencies
+      - ci
+    commit-message:
+      prefix: "chore(deps-ci)"

falsegreen-0.1.0/.github/pull_request_template.md

@@ -0,0 +1,44 @@
+<!--
+Thanks for sending a pull request. A few notes before you submit:
+
+- Keep this PR small and focused. One logical change per PR.
+- Three commits is the comfortable ceiling for review. Squash on merge is the
+  default, so you do not need to keep many commits.
+- Tests are expected for every behaviour change. See CONTRIBUTING.md.
+
+PR title must follow Conventional Commits:  <type>(<scope>): <description>
+Valid types: feat / fix / docs / refactor / test / chore / ci. Examples:
+
+  feat(scanner): detect skip() inside a broad except (C17)
+  fix(scanner): stop flagging len(x) == N as a weak check (C6)
+-->
+
+## Summary
+
+<!-- One or two sentences describing the change. -->
+
+## Changes
+
+- ...
+
+## Test plan
+
+- [ ] `pytest -q`
+- [ ] `python -m falsegreen src tests` (the tool must stay clean on itself)
+- [ ] `ruff check src tests`
+- [ ] `diff src/falsegreen/scanner.py skills/falsegreen/scripts/scan.py` (identical)
+
+## Checklist
+
+- [ ] A new/changed detection rule touches all four places: scanner logic,
+      `reference.md`, `docs/guide.md` (if a new case), and `tests/`.
+- [ ] For a new rule: a test proves it fires on the bad pattern AND a test proves
+      it does NOT fire on the legitimate look-alike.
+- [ ] HIGH-confidence codes were stress-tested against legitimate look-alikes
+      before being set to HIGH (they block commits).
+- [ ] No `Co-Authored-By:` AI agent trailers in the commit history.
+- [ ] Commit count is reasonable for review (rule of thumb: at most 3).
+
+## Related issues
+
+<!-- Fixes #123, Refs #456 -->

falsegreen-0.1.0/.github/release-drafter.yml

@@ -0,0 +1,54 @@
+# Release-drafter keeps a draft GitHub Release in sync with merged PRs on `main`.
+# Each merge appends a line under the category matching one of the PR's labels.
+# When you ship, bump the version on the draft and click Publish.
+# The workflow that consumes this file is .github/workflows/release-drafter.yml.
+
+name-template: "v$RESOLVED_VERSION"
+tag-template: "v$RESOLVED_VERSION"
+
+template: |
+  ## What's changed since $PREVIOUS_TAG
+
+  $CHANGES
+
+  **Full changelog**: https://github.com/$OWNER/$REPOSITORY/compare/$PREVIOUS_TAG...v$RESOLVED_VERSION
+
+categories:
+  - title: ":rocket: Features"
+    labels: [enhancement, feature]
+  - title: ":bug: Bug fixes"
+    labels: [bug, fix]
+  - title: ":lock: Security"
+    labels: [security]
+  - title: ":book: Documentation"
+    labels: [documentation, docs]
+  - title: ":hammer: Maintenance"
+    labels: [chore, dependencies, ci]
+
+autolabeler:
+  - label: enhancement
+    title: ['/^feat(\(.+\))?!?:/']
+  - label: bug
+    title: ['/^fix(\(.+\))?!?:/']
+  - label: documentation
+    title: ['/^docs(\(.+\))?!?:/']
+  - label: chore
+    title: ['/^(chore|build|ci|refactor|test|perf|revert)(\(.+\))?!?:/']
+  - label: breaking-change
+    title: ['/^[a-z]+(\(.+\))?!:/']
+
+change-template: "- $TITLE (#$NUMBER) by @$AUTHOR"
+change-title-escapes: '\<*_&'
+
+version-resolver:
+  major:
+    labels: [breaking-change, major]
+  minor:
+    labels: [enhancement, feature, minor]
+  patch:
+    labels: [bug, fix, security, documentation, docs, chore, dependencies, ci, patch]
+  default: patch
+
+exclude-labels:
+  - skip-changelog
+  - no-release

falsegreen-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,32 @@
+name: ci
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.8", "3.11", "3.13"]
+    steps:
+      - uses: actions/checkout@v6
+      - uses: actions/setup-python@v6
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install
+        run: |
+          python -m pip install --upgrade pip
+          pip install -e ".[dev]"
+      - name: Lint
+        run: ruff check src tests
+      - name: Test
+        run: pytest -q
+      - name: Bundled skill scanner must match the package
+        run: diff -u src/falsegreen/scanner.py skills/falsegreen/scripts/scan.py
+      - name: Self-scan (must flag the demo, must not flag itself)
+        run: |
+          python -m falsegreen skills/falsegreen/examples/bad_tests_sample.py || true
+          python -m falsegreen src tests

falsegreen-0.1.0/.github/workflows/release-drafter.yml

@@ -0,0 +1,21 @@
+name: release-drafter
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    types: [opened, reopened, synchronize]
+
+permissions:
+  contents: read
+
+jobs:
+  update_release_draft:
+    permissions:
+      contents: write
+      pull-requests: write
+    runs-on: ubuntu-latest
+    steps:
+      - uses: release-drafter/release-drafter@v6
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

falsegreen-0.1.0/.github/workflows/release.yml

@@ -0,0 +1,55 @@
+name: release
+
+# Builds the package and publishes it to PyPI via Trusted Publishing (OIDC).
+# No API token: the publish job exchanges a short-lived OIDC identity with PyPI.
+# Fires on a GitHub release being published, or manually for an existing tag.
+#
+# One-time human setup before the first run (see RELEASE.md / the issue):
+#   1. PyPI: add a Trusted Publisher for project `falsegreen`
+#      (owner vinicq, repo falsegreen, workflow release.yml, environment pypi).
+#   2. GitHub: create an environment named `pypi` (optionally tag-only + reviewer).
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@df4cb1c069e1874edd31b4311f1884172cec0e10  # v6
+      - uses: actions/setup-python@a309ff8b426b58ec0e2a45f0f869d46889d02405  # v6
+        with:
+          python-version: "3.13"
+      - name: Build sdist and wheel
+        run: |
+          python -m pip install --upgrade build twine
+          python -m build
+          python -m twine check dist/*
+      - name: Upload dist artifact
+        uses: actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02  # v4
+        with:
+          name: dist
+          path: dist/
+          if-no-files-found: error
+
+  publish:
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write  # OIDC: the only credential the publish step needs
+    steps:
+      - name: Download dist artifact
+        uses: actions/download-artifact@d3f86a106a0bac45b974a628896c90dbdf5c8093  # v4
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to PyPI
+        # Docker action: its ghcr.io image is tagged by release, not commit SHA,
+        # so a SHA pin fails to pull. release/v1 is the maintained, recommended ref.
+        uses: pypa/gh-action-pypi-publish@release/v1

falsegreen-0.1.0/.gitignore

@@ -0,0 +1,12 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+*.egg-info/
+build/
+dist/
+.venv/
+venv/
+.env
+.handoff/

falsegreen-0.1.0/.pre-commit-hooks.yaml

@@ -0,0 +1,8 @@
+- id: falsegreen
+  name: falsegreen (false-positive scanner)
+  description: Flag unit tests that pass without protecting anything.
+  entry: falsegreen --staged
+  language: python
+  types: [python]
+  pass_filenames: false
+  require_serial: true

falsegreen-0.1.0/CHANGELOG.md

@@ -0,0 +1,46 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and this project adheres
+to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-06-03
+
+First release.
+
+### Added
+- Deterministic AST scanner for Python/pytest (`falsegreen`, `python -m falsegreen`)
+  covering false-positive patterns across the semantic-logic families. HIGH codes
+  block a commit; LOW codes warn. Codes: C1 C2 C2b C3 C4 C4b C5 C6 C7 C8 C9 C13
+  C13b C14 C16 C17 C18 C19 C20 C21 CC. Each code carries a judgment tag (J1-J6).
+- C18 (LOW): assertion comparing `str()`/`repr()`/an f-string of a value to a
+  string literal, which checks formatting instead of the value (Sensitive Equality).
+- C19 (LOW): a `pytest.raises` block wrapping more than one statement, where an
+  earlier line can raise and the intended call is never reached.
+- PyPI publishing via Trusted Publishing (OIDC) in `.github/workflows/release.yml`;
+  see `RELEASE.md`.
+- Inline suppression (`# falsegreen: ignore[C8]`) and `--disable` flag.
+- Project config: `[tool.falsegreen]` in `pyproject.toml` or `.falsegreen.toml`
+  (`disable`, `exclude`, per-code `severity`); precedence CLI > inline > config.
+- Baseline / ratchet mode (`--baseline`, `--write-baseline`) with content
+  fingerprints that survive line shifts, for adopting on a legacy repo.
+- Output formats: `--format {text,json,sarif,junit}`, `--summary`, `--output`.
+  SARIF 2.1.0 carries the judgment tag; `--summary` rolls up by code and judgment.
+- C20 (HIGH): assertion in dead code after `return`/`raise`/`fail()`. C21 (LOW):
+  every assertion conditional, none runs unconditionally. Both from the rotten-
+  green-test line of work (Soares 2023).
+- Claude Code skill (`/falsegreen`) for the semantic pass: judges a test's
+  expected value against intended behavior using an oracle hierarchy and a
+  test-intent classification step (catches cases 12 and 18).
+- Distribution as a pip package, a `pre-commit` hook, and a Claude plugin.
+- Plain-language guide (`docs/guide.md`), detection reference, and a demo file.
+
+### Validated
+- Two real-project passes (bailiff, md-bridge) settled the rules and fixed three
+  false positives: C6 on called boolean predicates, C1 on literal-collection
+  loops, and C7 on `f() is f()` (the lru_cache / singleton identity test).
+
+[Unreleased]: https://github.com/vinicq/falsegreen/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/vinicq/falsegreen/releases/tag/v0.1.0

falsegreen-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,83 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at **vinicq@gmail.com**. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

falsegreen-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,107 @@
+# Contributing to falsegreen
+
+Thanks for helping. falsegreen finds unit tests that give false positives. The
+bar for a contribution is simple: the tool itself must not become a false
+positive. A new rule that cries wolf is worse than no rule.
+
+## 30-second cheat sheet
+
+```bash
+git clone https://github.com/vinicq/falsegreen
+cd falsegreen
+pip install -e ".[dev]"     # runtime has no deps; this adds pytest + ruff
+pytest -q                   # run the test suite
+python -m falsegreen src tests   # the tool must stay clean on itself
+ruff check src tests        # lint
+```
+
+Then branch, change, add a test, and open a pull request.
+
+## How the project is built
+
+Two layers, one repo:
+
+- **Scanner** (`src/falsegreen/scanner.py`): a zero-dependency AST pass. It parses
+  test files, it never imports or runs them. Each pattern is a case code
+  (`C1`, `C5`, `C13`, ...). HIGH-confidence codes block a commit; LOW only warn.
+- **Skill** (`skills/falsegreen/`): the Claude Code semantic pass. It bundles a
+  byte-identical copy of the scanner at `skills/falsegreen/scripts/scan.py`; CI
+  fails if it drifts from `src/falsegreen/scanner.py`.
+
+The plain-language rubric is `docs/guide.md`; the detection reference is
+`skills/falsegreen/reference.md`.
+
+## Filing an issue
+
+A useful bug report for a false positive includes the smallest test snippet that
+gets wrongly flagged, the code falsegreen emitted, and what you expected. For a
+false negative, show the bad test that slipped through. Use the demo file
+`skills/falsegreen/examples/bad_tests_sample.py` as a format reference.
+
+## Adding or changing a detection rule
+
+This is the most common contribution. A rule touches up to five places, and the
+pull request needs all that apply:
+
+1. **Logic** in `src/falsegreen/scanner.py`. Decide HIGH vs LOW. The rule of
+   thumb: HIGH only if a legitimate test can almost never trigger it, because
+   HIGH blocks commits. When in doubt, ship it LOW.
+2. **Reference** entry in `skills/falsegreen/reference.md` (what it looks like,
+   why it fools you, confidence, the tool it maps to).
+3. **Guide** entry in `docs/guide.md` if it is a new case, in the same
+   real-world-analogy style as the others.
+4. **Tests** in `tests/test_scanner.py`: one test proving the rule fires on the
+   bad pattern, and at least one proving it does NOT fire on the legitimate
+   look-alike. The second test matters more than the first.
+5. **Skill prose** in `skills/falsegreen/SKILL.md`, *only if* the change alters a
+   confidence level, an exemption, a flag, or the operator's mental model. CI
+   byte-checks `scripts/scan.py` against the scanner, so detector *logic* is
+   mirrored automatically; the SKILL.md prose and its flag list are NOT, so they
+   must be kept consistent with `reference.md` and the README CLI section by hand.
+
+Then run `pytest`, `python -m falsegreen src tests` (must stay clean), and
+`diff src/falsegreen/scanner.py skills/falsegreen/scripts/scan.py` (must be
+identical, copy the file if you changed the scanner).
+
+### The false-positive policy
+
+falsegreen blocks commits, so precision beats recall. A rule that wrongly blocks
+one legitimate test will get the whole tool disabled. Before promoting a rule to
+HIGH, try to break it: parametrized tests, fixtures that assert, abstract base
+test classes, `@patch`-injected mocks, helper functions. If any of those trips
+it, keep it LOW or tighten the heuristic.
+
+## Tests are required
+
+No behavior change merges without a test. The detector of false positives cannot
+have any of its own. Every legitimate-code counter-example you can think of
+should have a test asserting the scanner stays quiet on it.
+
+## Commit messages: Conventional Commits
+
+Format: `type(scope): summary`. Recognised types: `feat`, `fix`, `docs`,
+`test`, `refactor`, `chore`, `ci`. Examples:
+
+```
+feat(scanner): detect skip() inside a broad except (C17)
+fix(scanner): stop flagging len(x) == N as a weak check (C6)
+docs(guide): add the bug-freezing case (18)
+```
+
+Keep a pull request to roughly three commits. Squash noise before review.
+
+## Authorship and AI tooling
+
+Use any tools you like, including AI assistants. But the authorship is yours.
+Do not add `Co-Authored-By` trailers for AI agents, and do not add AI agents to
+the contributor list. Human co-authors are welcome and encouraged.
+
+## License
+
+By contributing, you agree that your contributions are licensed under the MIT
+License (see `LICENSE`).
+
+## Code of conduct
+
+This project follows the [Contributor Covenant](CODE_OF_CONDUCT.md). Be
+respectful, assume good faith, report problems to `vinicq@gmail.com`.

falsegreen-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Vinicius Queiroz
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.