ghostcite 0.1.0__tar.gz

ghostcite-0.1.0/.editorconfig

@@ -0,0 +1,21 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+
+[*.py]
+indent_size = 4
+max_line_length = 100
+
+[*.{yml,yaml,json,toml}]
+indent_size = 2
+
+[*.md]
+trim_trailing_whitespace = false
+
+[Makefile]
+indent_style = tab

ghostcite-0.1.0/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,62 @@
+name: Bug report
+description: Report a bug in ghostcite
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing a bug. Please do **not** report security vulnerabilities here —
+        see [SECURITY.md](../SECURITY.md) for private disclosure.
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: A clear description of the bug and what you expected instead.
+      placeholder: I ran `ghostcite refs.bib` and expected ... but got ...
+    validations:
+      required: true
+  - type: dropdown
+    id: component
+    attributes:
+      label: Which component?
+      multiple: true
+      options:
+        - CLI (ghostcite command)
+        - CrossRef lookup
+        - PubMed cross-check
+        - Input parser (BibTeX / Markdown / DOI list)
+        - output / formatting
+        - not sure
+    validations:
+      required: true
+  - type: input
+    id: version
+    attributes:
+      label: ghostcite version
+      description: Output of `ghostcite --version`.
+      placeholder: "0.1.0"
+    validations:
+      required: true
+  - type: input
+    id: os
+    attributes:
+      label: OS / platform
+      description: e.g. Ubuntu 24.04, macOS 14, WSL2, Windows 11.
+    validations:
+      required: true
+  - type: textarea
+    id: repro
+    attributes:
+      label: Steps to reproduce
+      description: The exact command and a minimal `.bib` snippet (redact any private DOIs if needed).
+      render: shell
+    validations:
+      required: true
+  - type: textarea
+    id: output
+    attributes:
+      label: Actual output / error
+      description: Full terminal output, including any tracebacks.
+      render: shell
+    validations:
+      required: false

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

@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Security vulnerability
+    url: https://github.com/musharna/ghostcite/security/advisories/new
+    about: Report security issues privately — do not open a public issue.

ghostcite-0.1.0/.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,25 @@
+name: Feature request
+description: Suggest an enhancement to ghostcite
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem are you trying to solve?
+      description: The use case or pain point behind the request.
+    validations:
+      required: true
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: What you'd like ghostcite to do. Note which component it touches (CrossRef lookup, PubMed check, parser, CLI, output).
+    validations:
+      required: true
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Other approaches or workarounds you've tried.
+    validations:
+      required: false

ghostcite-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,28 @@
+<!-- Thanks for contributing to ghostcite! -->
+
+## What does this PR do?
+
+<!-- A short description of the change and the motivation. Link any related issue. -->
+
+Fixes #
+
+## Component(s) touched
+
+<!-- Check all that apply -->
+
+- [ ] core checker (`ghostcite/checker.py`)
+- [ ] CrossRef client (`ghostcite/crossref.py`)
+- [ ] PubMed client (`ghostcite/pubmed.py`)
+- [ ] BibTeX parser (`ghostcite/parser.py`)
+- [ ] CLI (`ghostcite/cli.py`)
+- [ ] docs / CI / packaging
+
+## Checklist
+
+- [ ] `uv run --extra dev ruff check .` passes
+- [ ] `uv run --extra dev ruff format --check .` passes
+- [ ] `uv run --extra dev pytest -m "not live" -q` passes
+- [ ] Coverage stays at or above 85 % (`--cov=ghostcite --cov-fail-under=85`)
+- [ ] Added/updated tests for the change (used the `live` marker only where a real API call is genuinely required)
+- [ ] Updated `CHANGELOG.md` for any user-facing change
+- [ ] Updated docs (`README.md`, `docs/`) if install/usage/config surface changed

ghostcite-0.1.0/.github/dependabot.yml

@@ -0,0 +1,25 @@
+version: 2
+updates:
+  # Python dependencies (pyproject.toml + uv.lock)
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    groups:
+      python-minor-patch:
+        update-types:
+          - "minor"
+          - "patch"
+
+  # GitHub Actions used in .github/workflows
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    open-pull-requests-limit: 5
+    groups:
+      actions-minor-patch:
+        update-types:
+          - "minor"
+          - "patch"

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

@@ -0,0 +1,63 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: true
+
+permissions:
+  contents: read
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.9", "3.11", "3.13"]
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78 # v7.6.0
+        with:
+          python-version: ${{ matrix.python-version }}
+          enable-cache: true
+
+      - name: Tests + coverage (excluding live CrossRef/NCBI calls)
+        run: uv run --extra dev pytest --cov=ghostcite --cov-report=term-missing -m "not live"
+
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78 # v7.6.0
+        with:
+          enable-cache: true
+
+      - name: Lint (ruff)
+        run: uv run --extra dev ruff check .
+
+      - name: Format check (ruff)
+        run: uv run --extra dev ruff format --check .
+
+  types:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78 # v7.6.0
+        with:
+          enable-cache: true
+
+      # mypy is clean and now gates the build: type regressions fail CI.
+      - name: Types (mypy)
+        run: uv run --extra dev mypy src/ghostcite

ghostcite-0.1.0/.github/workflows/codeql.yml

@@ -0,0 +1,36 @@
+name: CodeQL
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+  schedule:
+    # Weekly, Mondays at 07:00 UTC
+    - cron: "0 7 * * 1"
+
+jobs:
+  analyze:
+    name: Analyze
+    runs-on: ubuntu-latest
+    permissions:
+      security-events: write
+      contents: read
+      actions: read
+    strategy:
+      fail-fast: false
+      matrix:
+        language: ["python"]
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+
+      - name: Initialize CodeQL
+        uses: github/codeql-action/init@v4
+        with:
+          languages: ${{ matrix.language }}
+
+      - name: Perform CodeQL Analysis
+        uses: github/codeql-action/analyze@v4
+        with:
+          category: "/language:${{ matrix.language }}"

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

@@ -0,0 +1,92 @@
+name: Release
+
+# Tag-driven release: push a `vX.Y.Z` tag and this builds, publishes to PyPI
+# via Trusted Publishing (OIDC — no API token stored anywhere), and cuts a
+# GitHub release with the artifacts attached.
+#
+#   git tag v0.1.0 && git push origin v0.1.0
+#
+# One-time setup required on PyPI: project `ghostcite` → Settings → Publishing →
+# add a GitHub Actions trusted publisher (owner=musharna, repo=ghostcite,
+# workflow=release.yml, environment=pypi). And create a GitHub environment
+# named `pypi` (Settings → Environments).
+
+on:
+  push:
+    tags: ["v*"]
+
+jobs:
+  build:
+    name: Build distributions
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+      - name: Install uv
+        uses: astral-sh/setup-uv@37802adc94f370d6bfd71619e3f0bf239e1f3b78 # v7.6.0
+      - name: Verify tag matches package version
+        run: |
+          TAG="${GITHUB_REF_NAME#v}"
+          VER=$(python3 -c "import tomllib; print(tomllib.load(open('pyproject.toml','rb'))['project']['version'])")
+          if [ "$TAG" != "$VER" ]; then
+            echo "Release tag '$TAG' != pyproject version '$VER'"; exit 1
+          fi
+      - name: Build sdist + wheel
+        run: uv build
+      - name: Upload artifacts
+        uses: actions/upload-artifact@v7
+        with:
+          name: dist
+          path: dist/
+
+  pypi:
+    name: Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write # OIDC token for Trusted Publishing; no password/token needed
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+      - name: Publish to PyPI (trusted publishing)
+        uses: pypa/gh-action-pypi-publish@cef221092ed1bacb1cc03d23a2d87d1d172e277b # v1.14.0
+
+  github-release:
+    name: Create GitHub release
+    needs: pypi
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write # create the release + upload assets
+    steps:
+      - uses: actions/checkout@v6 # for CHANGELOG.md
+      - uses: actions/download-artifact@v8
+        with:
+          name: dist
+          path: dist/
+      - name: Create release with artifacts
+        env:
+          GH_TOKEN: ${{ github.token }}
+        run: |
+          # Prefer the matching CHANGELOG.md section as release notes; fall back
+          # to GitHub's auto-generated notes if the version has no section.
+          VER="${GITHUB_REF_NAME#v}"
+          awk -v h="## [$VER]" '
+            index($0, h) == 1 { grab = 1; next }
+            grab && index($0, "## ") == 1 { exit }
+            grab { print }
+          ' CHANGELOG.md > release-notes.md
+          if grep -q '[^[:space:]]' release-notes.md; then
+            gh release create "${GITHUB_REF_NAME}" \
+              --repo "${GITHUB_REPOSITORY}" \
+              --title "${GITHUB_REF_NAME}" \
+              --notes-file release-notes.md \
+              dist/*
+          else
+            gh release create "${GITHUB_REF_NAME}" \
+              --repo "${GITHUB_REPOSITORY}" \
+              --title "${GITHUB_REF_NAME}" \
+              --generate-notes \
+              dist/*
+          fi

ghostcite-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+dist/
+build/
+*.egg-info/
+.venv/
+uv.lock
+
+# local dev artifacts (design spec + implementation plan) — not shipped publicly
+docs/

ghostcite-0.1.0/.pre-commit-config.yaml

@@ -0,0 +1,16 @@
+repos:
+  - repo: https://github.com/pre-commit/pre-commit-hooks
+    rev: v6.0.0
+    hooks:
+      - id: trailing-whitespace
+        exclude: '\.md$'
+      - id: end-of-file-fixer
+      - id: check-yaml
+      - id: check-toml
+
+  - repo: https://github.com/astral-sh/ruff-pre-commit
+    rev: v0.15.16
+    hooks:
+      - id: ruff
+        args: [--fix]
+      - id: ruff-format

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

@@ -0,0 +1,10 @@
+- id: ghostcite
+  name: ghostcite (ghost-citation check)
+  description: Catch citations whose claimed author/year does not match the DOI's CrossRef record.
+  entry: ghostcite
+  language: python
+  files: \.(bib|md)$
+  # ghostcite's CLI takes exactly one positional bibliography file, but pre-commit
+  # would auto-append every matched staged file. Disable that and have users name
+  # their file explicitly via `args:` in .pre-commit-config.yaml.
+  pass_filenames: false

ghostcite-0.1.0/CHANGELOG.md

@@ -0,0 +1,38 @@
+# Changelog
+
+All notable changes to this project are documented here. The format is based on
+[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).
+
+## [0.1.0] - 2026-06-08
+
+Initial release.
+
+### Added
+
+- CrossRef author/year cross-check: compares each citation's claimed first-author
+  surname and year against CrossRef's canonical record for the DOI.
+- Input auto-detection for BibTeX, Markdown reference lists, and bare DOI lists
+  (override with `--format {auto,bibtex,markdown,doi}`).
+- Read the bibliography from stdin by passing `-` as the filename
+  (e.g. `cat refs.bib | ghostcite -`).
+- Severity tiers: A (author mismatch), B (year mismatch), C (cosmetic fold-only),
+  R (retraction / expression-of-concern), U (unresolvable / not verifiable).
+- Retraction and expression-of-concern detection via CrossRef `updated-by` /
+  `update-to` / `relation` metadata.
+- `--cross-check pubmed`: optional second source of truth via PubMed / NCBI
+  E-utilities. Corroborates or conflicts CrossRef findings, can raise findings
+  CrossRef missed, and supplies records for DOIs absent from CrossRef. Honors
+  `--ncbi-email` / `--ncbi-api-key` (or `NCBI_EMAIL` / `NCBI_API_KEY`) for NCBI
+  etiquette and a higher rate limit.
+- Proactive rate pacing: self-throttles to CrossRef's advertised rate limit (read
+  from response headers); `--max-rps` to cap further.
+- `--color {auto,always,never}` colorized tier glyphs, honoring `NO_COLOR`.
+- No-DOI entries resolved by best-effort bibliographic search, flagged
+  low-confidence and never escalated above a warning on their own.
+- `--json` machine-readable output, `--dry-run` parse-and-count (no network), and
+  `--fail-on` CI gate to select which tiers force a non-zero exit.
+- `--version` flag and `python -m ghostcite` module entry point.
+- Composite GitHub Action (`musharna/ghostcite@v1`) for drop-in CI usage.
+- Exit-code policy: `0` clean, `1` findings at/above the fail threshold, `2` tool
+  error (network down, unparseable input).

ghostcite-0.1.0/CITATION.cff

@@ -0,0 +1,25 @@
+cff-version: 1.2.0
+message: "If you use ghostcite in your work, please cite it as below."
+title: ghostcite
+abstract: >-
+  A deterministic, no-LLM command-line tool that catches ghost citations —
+  references whose claimed author or year does not match the canonical record
+  for the DOI at CrossRef (and optionally PubMed) — and flags retracted or
+  expression-of-concern works.
+type: software
+authors:
+  - family-names: Arnold
+    given-names: Jaret
+    orcid: "https://orcid.org/0009-0003-4055-5238"
+repository-code: "https://github.com/musharna/ghostcite"
+url: "https://github.com/musharna/ghostcite"
+license: MIT
+version: 0.1.0
+date-released: "2026-06-08"
+keywords:
+  - citations
+  - crossref
+  - pubmed
+  - bibtex
+  - research-integrity
+  - doi

ghostcite-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 by opening an issue at <https://github.com/musharna/ghostcite/issues> or via GitHub's private advisory mechanism. 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

ghostcite-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,85 @@
+# Contributing to ghostcite
+
+Thanks for your interest in ghostcite — a deterministic, no-LLM Python CLI that catches ghost citations by cross-checking a bibliography's claimed author/year against CrossRef, with optional PubMed verification and retraction flagging.
+
+## Dev environment setup
+
+ghostcite uses [`uv`](https://docs.astral.sh/uv/) for dependency management. CI resolves
+dependencies on the fly via `uv run --extra dev ...` (there is no committed lockfile;
+`uv.lock` is gitignored, so there is no frozen-lockfile gate). Mirror it locally:
+
+```bash
+# install all extras the test/lint/type checks need
+uv sync --extra dev
+```
+
+This installs the `dev` tools (pytest, pytest-httpx, ruff, mypy, coverage). Requires **Python ≥ 3.9** (CI tests 3.9, 3.11, and 3.13).
+
+## Running the checks (what CI runs)
+
+CI (`.github/workflows/ci.yml`) runs these (tests on the 3.9 / 3.11 / 3.13 matrix). Run them locally before opening a PR:
+
+```bash
+# Lint + format check (gates the build)
+uv run --extra dev ruff check .
+uv run --extra dev ruff format --check .
+
+# Tests, excluding tests that hit real external APIs
+uv run --extra dev pytest -m "not live" -q
+
+# Coverage gate (85 % floor)
+uv run --extra dev pytest -m "not live" --cov=ghostcite --cov-fail-under=85 -q
+
+# Type-check (hard CI gate — type errors fail the build)
+uv run --extra dev mypy src/ghostcite
+```
+
+### Tests and the `live` marker
+
+Most of the suite runs against in-process fixtures (pytest-httpx mocks CrossRef/NCBI responses). Tests marked `live` hit the **real CrossRef API** (and optionally NCBI E-utilities) and are skipped by default in CI.
+
+To run them locally:
+
+```bash
+# Basic live probes (CrossRef only)
+uv run --extra dev pytest -m live -q
+
+# With PubMed cross-check (supply your NCBI API key for higher rate limits)
+NCBI_API_KEY=<your-key> uv run --extra dev pytest -m live -q
+```
+
+Live tests should be rare, narrowly scoped (a single known-good DOI + a known ghost), and must not assert on network-variable fields.
+
+### Linting & formatting
+
+Ruff is configured in `pyproject.toml` (`line-length = 100`, `target-version = py39`).
+`uv run --extra dev ruff check .` is the gate; `uv run --extra dev ruff check --fix .` and
+`uv run --extra dev ruff format .` apply autofixes.
+
+### Type-checking
+
+`uv run --extra dev mypy src/ghostcite` is a **hard CI gate** (the `types` job has no `continue-on-error`, so type errors fail the build). Keep it green — add annotations to new/changed code.
+
+## Running ghostcite locally for manual testing
+
+```bash
+# Check a BibTeX file
+uv run --extra dev ghostcite refs.bib
+
+# Read from stdin (pipe from another tool)
+cat refs.bib | uv run --extra dev ghostcite -
+
+# With PubMed cross-check and colored output
+uv run --extra dev ghostcite --cross-check pubmed --color always refs.bib
+
+# Never fail the exit code (report only, no CI gate)
+uv run --extra dev ghostcite --fail-on none refs.bib
+```
+
+## Commits & pull requests
+
+- **CI must pass.** Ruff, the `not live` test suite, and the 85 % coverage gate must be green across the full Python matrix.
+- Keep changes focused and add tests for new behavior. Use the `live` marker only for tests that genuinely need to hit a real external API.
+- Update [`CHANGELOG.md`](CHANGELOG.md) for any user-facing change.
+- Update docs (`README.md`, `docs/`) when you change install/usage/config surface.
+- **Commit style:** conventional commits (`fix:`, `feat:`, `docs:`, `chore:`, `test:`, `refactor:`). No trailers required.

ghostcite-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Jaret Arnold
+
+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.