release capa as pypi project `capa`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 6.2k
- Forks
- 726
- Avg merge
- 11d 11h
- Merged PRs (30d)
- 7
Description
we got control of the pypi package `capa` so should we publish to that package instead? we currently use `flare-capa`. if we're going to do it, v2.0 is the time.
alternatively, we could publish to both names?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. First review how the project currently publishes `flare-capa` and what would be required for the PyPI name `capa`, then resolve whether to publish under one name or both at v2.0. Done means the release naming decision and its migration scope are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100