pryscraper/.forgejo/ISSUE_TEMPLATE/bug.yml
cryptorugmunch bb77eb5f35 chore(license): re-license to dual MIT (core) + BSL 1.1 (stealth)
Re-license Pry from full Proprietary to a dual-license model:

- Core engine, extraction, templates (80+), MCP server, x402 payment rail,
  CLI, SDK, browser extension, WordPress plugin, Shopify app, and
  llm_providers: MIT (see LICENSE)
- Anti-detection / stealth subset (15 files): BSL 1.1 with Change Date
  2029-01-01 (see LICENSE-BSL-STEALTH)

BSL files (anti-detection moat):
  ultimate_scraper.py, stealth_engine.py, stealth_scripts/*.js (6),
  camoufox_integration.py, tls_fingerprint.py, cookie_warmer.py,
  behavioral_biometrics.py, adaptive.py, browser_pool.py, network.py,
  captcha_solver.py, shadow_dom.py, lazy_load.py, signup_automator.py,
  auth_connector.py

This enables community contributions to the core engine (templates,
integrations, MCP tools) while protecting the anti-detection techniques
that constitute the actual competitive moat. BSL Additional Use Grant
permits free non-production use; production deployment requires a
commercial license from enterprise@rugmunch.io.

Changes:
- Replace proprietary LICENSE with MIT LICENSE + new LICENSE-BSL-STEALTH
- Add SPDX-License-Identifier headers to 300+ source files
- Add docs/adr/0002-dual-licensing.md (ADR documenting the decision)
- Update README.md: new License section with BSL Additional Use Grant
- Update LICENSING_PRICING_STRATEGY.md: Section 3 (PryScraper) for dual license
- Update AGENTS.md: license line in header + new rule 8 (PRs touching BSL rejected)
- Update pyproject.toml: license = "MIT AND BSL-1.1" + classifiers + license-files
- Update DECISIONS.md index with ADR-0002
- Update STATUS.md (2026-07-03) and PLAN.md sprint goals

Refs: ADR-0002
2026-07-02 19:49:21 +02:00

90 lines
2.3 KiB
YAML

# SPDX-License-Identifier: MIT
# Copyright (c) 2026 Rug Munch Media LLC
# Part of Pry — https://git.rugmunch.io/RugMunchMedia/pryscraper
# Licensed under MIT. See LICENSE.
name: Bug Report
description: Report a defect or unexpected behavior
title: "[Bug]: "
labels: ["bug", "triage"]
body:
- type: markdown
attributes:
value: |
Thanks for reporting a bug. Please fill in the sections below.
- type: input
id: version
attributes:
label: Version
description: Tag, branch, or commit SHA where the bug reproduces
placeholder: "v1.2.3 or main@abc1234"
validations:
required: true
- type: dropdown
id: severity
attributes:
label: Severity
description: How bad is the impact?
options:
- Critical (data loss, security, total outage)
- High (major feature broken, no workaround)
- Medium (feature broken, workaround exists)
- Low (minor, cosmetic)
validations:
required: true
- type: textarea
id: summary
attributes:
label: What happened?
description: Clear, factual description of the bug
placeholder: |
Expected: ...
Actual: ...
validations:
required: true
- type: textarea
id: repro
attributes:
label: Steps to reproduce
description: Numbered steps. Include URLs, commands, inputs.
placeholder: |
1. Go to /scanner/scan
2. Enter address 0x...
3. Click "Analyze"
4. See "undefined" instead of risk score
render: shell
validations:
required: true
- type: textarea
id: logs
attributes:
label: Logs / errors / stack trace
description: Paste relevant output. Use a code block.
render: shell
placeholder: |
```
2026-07-02T10:00:00 ERROR ...
```
- type: input
id: env
attributes:
label: Environment
description: OS, browser, runtime version, etc.
placeholder: "macOS 14.5, Chrome 125, Node 22.3"
- type: checkboxes
id: checks
attributes:
label: Pre-submit checks
options:
- label: I searched existing issues and didn't find a duplicate
required: true
- label: I can reproduce this on `main` HEAD
required: false
- label: I'm willing to submit a PR
required: false