From c15e847e682fdc70d89ae467820cb8e485579b64 Mon Sep 17 00:00:00 2001 From: Minsu Lee Date: Thu, 2 Jul 2026 01:19:43 +0900 Subject: [PATCH 1/2] chore: normalize LICENSE copyright to Passion Factory and add community-health files --- .github/ISSUE_TEMPLATE/bug_report.md | 31 +++++ .github/ISSUE_TEMPLATE/config.yml | 8 ++ .github/ISSUE_TEMPLATE/feature_request.md | 22 ++++ .github/PULL_REQUEST_TEMPLATE.md | 17 +++ CODE_OF_CONDUCT.md | 132 ++++++++++++++++++++++ CONTRIBUTING.md | 42 +++++++ LICENSE | 2 +- README.md | 3 + SECURITY.md | 39 +++++++ 9 files changed, 295 insertions(+), 1 deletion(-) create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md create mode 100644 .github/ISSUE_TEMPLATE/config.yml create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md create mode 100644 .github/PULL_REQUEST_TEMPLATE.md create mode 100644 CODE_OF_CONDUCT.md create mode 100644 CONTRIBUTING.md create mode 100644 SECURITY.md diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md new file mode 100644 index 0000000..45e3d02 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -0,0 +1,31 @@ +--- +name: Bug report +about: Report a problem to help us improve +title: "" +labels: ["bug"] +--- + +## Describe the bug + +A clear and concise description of what the bug is. + +## To reproduce + +Steps to reproduce the behavior: + +1. ... +2. ... +3. See error + +## Expected behavior + +What you expected to happen. + +## Environment + +- Package version: +- Runtime/OS: + +## Additional context + +Logs, screenshots, or anything else that helps. diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml new file mode 100644 index 0000000..af9041d --- /dev/null +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -0,0 +1,8 @@ +blank_issues_enabled: false +contact_links: + - name: Question or discussion + url: https://github.com/pleaseai/adaptive-fetch/discussions + about: Ask questions and discuss ideas here instead of opening an issue. + - name: Security vulnerability + url: https://github.com/pleaseai/adaptive-fetch/security/advisories/new + about: Report security issues privately — do not open a public issue. diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md new file mode 100644 index 0000000..f1cf4e8 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -0,0 +1,22 @@ +--- +name: Feature request +about: Suggest an idea or improvement +title: "" +labels: ["enhancement"] +--- + +## Problem + +What problem does this feature solve? What is the use case? + +## Proposed solution + +A clear and concise description of what you want to happen. + +## Alternatives considered + +Other approaches you've thought about, and why this one is preferable. + +## Additional context + +Anything else that helps explain the request. diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md new file mode 100644 index 0000000..733b8b9 --- /dev/null +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -0,0 +1,17 @@ + + +## Summary + + + +## Related issue + + + +## Checklist + +- [ ] PR title follows Conventional Commits +- [ ] Tests added or updated, and the suite passes (`cargo test`) +- [ ] Lint/format pass (`mise run check`) +- [ ] Documentation updated if behavior changed +- [ ] No breaking change, or a `BREAKING CHANGE:` note is included diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..c543ba4 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,132 @@ +# 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 email 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 +**conduct@pleaseai.dev**. +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 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md new file mode 100644 index 0000000..06cfce6 --- /dev/null +++ b/CONTRIBUTING.md @@ -0,0 +1,42 @@ +# Contributing + +Thanks for your interest in contributing! This guide covers how to get from a clone to a merged pull request. + +By participating, you agree to abide by our [Code of Conduct](./CODE_OF_CONDUCT.md). All documentation, code, comments, and commit messages in this repository are written in **English**. + +## Getting started + +```bash +git clone https://github.com/pleaseai/adaptive-fetch.git +cd adaptive-fetch +mise install # install pinned tool versions (rust + bun, see mise.toml) +cargo build # build the engine crate +``` + +## Development workflow + +1. Create a branch from the default branch (e.g. `feat/short-description` or `fix/issue-123`). +2. Make focused changes — keep each pull request to one logical change. +3. Run the checks below and make sure they pass. +4. Open a pull request and fill out the template. + +```bash +mise run check # fmt-check + clippy + test (mirrors CI) +cargo test # run the test suite +cargo build # ensure it builds +``` + +## Commit messages + +We follow [Conventional Commits](https://www.conventionalcommits.org/): `type(scope): subject`, where `type` is one of `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, etc. Breaking changes include a `BREAKING CHANGE:` footer. Versioning and the changelog are generated automatically from these messages, so accurate types matter. + +## Pull requests + +- Reference the issue your PR addresses (e.g. `Closes #123`). +- Use a Conventional-Commit-style PR title — it becomes the squash-merge commit. +- Make sure CI is green before requesting review. + +## Reporting bugs and requesting features + +Open an issue using the bug report or feature request template. For security +vulnerabilities, **do not** open a public issue — follow [SECURITY.md](./SECURITY.md). diff --git a/LICENSE b/LICENSE index f3af155..8b22ac3 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2026 pleaseai +Copyright (c) 2026 Passion Factory Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/README.md b/README.md index e0378da..e3a6c94 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,8 @@ # adaptive-fetch +[![CI](https://github.com/pleaseai/adaptive-fetch/actions/workflows/ci.yml/badge.svg)](https://github.com/pleaseai/adaptive-fetch/actions/workflows/ci.yml) +[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](./LICENSE) + A resilient, **site-agnostic** public-page reader for Claude Code. When a fetch is blocked (402 / 403 / WAF / CAPTCHA), `adaptive-fetch` automatically tries every bypass strategy until one works — no API keys, no proxy setup. diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..24b2c40 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,39 @@ +# Security Policy + +## Supported Versions + +Security fixes are provided for the latest released major version. Older +versions may receive fixes at the maintainers' discretion. + +| Version | Supported | +| ------- | ------------------ | +| latest | :white_check_mark: | +| older | :x: | + +## Reporting a Vulnerability + +**Please do not report security vulnerabilities through public GitHub issues, +discussions, or pull requests.** + +Instead, report them privately through GitHub's +[private vulnerability reporting](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability): +go to the repository's **Security** tab and click **"Report a vulnerability"**. + +If you cannot use that channel, email **security@pleaseai.dev** instead. + +Please include: + +- A description of the vulnerability and its impact +- Steps to reproduce, or a proof of concept +- Affected versions, and any known mitigations + +## What to Expect + +- We aim to acknowledge your report within **72 hours**. +- We will keep you informed of progress toward a fix and may ask for additional + detail. +- Once a fix is released, we will credit you in the advisory unless you prefer + to remain anonymous. + +We ask that you give us a reasonable opportunity to address the issue before any +public disclosure. From 6fe9f7ec2c3dac61b9fb8417f7fe9f4d986258e3 Mon Sep 17 00:00:00 2001 From: Minsu Lee Date: Thu, 2 Jul 2026 01:28:21 +0900 Subject: [PATCH 2/2] chore: apply AI code review suggestions --- CONTRIBUTING.md | 1 - 1 file changed, 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 06cfce6..cbbc5a9 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -22,7 +22,6 @@ cargo build # build the engine crate ```bash mise run check # fmt-check + clippy + test (mirrors CI) -cargo test # run the test suite cargo build # ensure it builds ```