phishdestroy / destroylist

Star History

190 days recorded, May 8, 2026 – Nov 13, 2026 (UTC). Net change +1,221 stars.

The star count of each day is the latest count minus the net stars of the later days.

Add this Star History to a README

The images follow the light or dark theme of the page that shows them, and update every hour. Add ?theme=light or ?theme=dark to the chart address to keep one theme.

Star History chart

[![Star History of phishdestroy/destroylist](https://awesomerepos.com/phishdestroy/destroylist/stars.svg)](https://awesomerepos.com/phishdestroy/destroylist) Copy

Badge

[![AwesomeRepos](https://awesomerepos.com/phishdestroy/destroylist/badge.svg)](https://awesomerepos.com/phishdestroy/destroylist) Copy

Timeline

1. Jul 17, 2025 Created on the Repository Host
2. Nov 8, 2025 Release v1.0.0
3. Jul 4, 2026 Reached 1,000 stars, 352 days after it was created
4. Jul 14, 2026 +103 stars in one day
5. Jul 16, 2026 Largest star day recorded: +183 stars
6. Jul 20, 2026 +123 stars in one day
7. Jul 20, 2026 Release archives
8. Oct 19, 2026 Release stix: STIX 2.1 bundle
9. Nov 12, 2026 Entered the Repository Index: 2,018 stars on 2026-11-12
10. Nov 13, 2026 Latest push

The timeline comes from the creation date and the releases on the Repository Host, the Admission, the Star History, and the Observations. Star milestones show only when the Star History records the day. The list shows up to 5 stable releases from the latest 10 releases recorded. When none of them is stable, one item counts the pre-releases. On the chart of net stars each day, a solid line marks each recorded release.

Forks and pushes

From 2 Observations, Nov 13, 2026 – Nov 14, 2026. Forks +3. AwesomeRepos saw a new push on 1 of 1 days.

Health facts

Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos reads the weekly commits, the changelog, and the community files each week for the 5,000 visible repositories with the most stars and for each rising repository. How AwesomeRepos defines each check

Improve the Health Facts of the GitHub repository phishdestroy/destroylist.

AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/phishdestroy/destroylist. A change to the repository can improve each of the item below. Each item gives the measured fact or score, and a task.

1. The newest release tag is a semantic version
   Fact: The newest release tag is stix.
   Rule: The tag of the newest release has the form 1.2.3 or v1.2.3, with an optional pre-release or build part. There is no data when the repository has no release.
   Task: Make the next release tag a semantic version (1.2.3 or v1.2.3). Do not change or delete a published tag. If a release tool makes the tags, configure it for semantic versions, and write the version scheme in the contributing guide.

Rules for this work:
- Each file must be true for this project. Do not copy text that does not apply to it.
- Do not choose a licence, a contact, or a release version for me. Ask me.
- Do not publish a release, change a repository setting, or push to the default branch. Make the changes on a new branch.
- Keep each change small, and run the checks of this repository before you finish.
- At the end, list each item as DONE, SKIPPED (with the reason), or NEEDS A DECISION (with the question).

AwesomeRepos reads these facts again in its next scan. The definitions of the checks: https://awesomerepos.com/health-facts

Observations

Latest Observation, Nov 14, 2026: 2,063 stars, 512 forks, last push Nov 13, 2026, not archived. One of 2 Observations since Nov 13, 2026.