Carapacik / swagger_parser
Generate Dart models and HTTP clients from Swagger 2.0 and OpenAPI 3.0–3.2. Supports JSON, YAML, Retrofit, Dio, package:http, and custom templates.
- Stars
- 307 stars
- Forks
- 110 forks
- Language
- Dart
- License
- MIT
- Created
- Oct 2, 2022
- Last push
- Nov 11, 2026
- Updated
- Nov 11, 2026
Why these Tags: an agent read the README and quoted it
- OpenAPI tool from the description:
Generate Dart models and HTTP clients from Swagger 2.0 and OpenAPI 3.0–3.2.
An agent gave these Tags from the fixed Tag list in the AwesomeRepos source code. A code check kept each Tag only when its quote is in the text. A wrong Tag? Report an error with the form at the end of this page.
Admitted to the Repository Index on Nov 11, 2026: +136 stars in 7 days.
Star History
156 days recorded, Jun 10, 2026 – Nov 12, 2026 (UTC). Net change +163 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
[](https://awesomerepos.com/Carapacik/swagger_parser) Badge
[](https://awesomerepos.com/Carapacik/swagger_parser) Timeline
It gained stars on 5 of the 156 days recorded since Jun 10, 2026.
Its largest 7 days were Nov 4, 2026 to Nov 10, 2026: 160 stars.
In the 30 days to Nov 12, 2026 it got 160 stars, 15900% more than in the 30 days before.
It had 144 stars before Jun 10, 2026 and has 307 stars now: 193 fewer than 500.
- Created on the Repository Host
- +1 stars in one day
- +1 stars in one day
- Largest star day recorded: +159 stars, the same day as release 2.0.0
- Release 2.0.0
- Entered the Repository Index: +136 stars in 7 days
- 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 12, 2026 – Nov 13, 2026. Forks 0. AwesomeRepos saw a new push on 0 of 1 days.
- Nov 13, 2026: no new push
A filled day: the last push time changed since the Observation before it.
Health facts
Measured facts in four separate dimensions, each with a date and a source. AwesomeRepos does not add them into one score. AwesomeRepos last read these facts from GitHub on Nov 13, 2026. How AwesomeRepos defines each check
Copies a prompt for a coding agent. It has 2 tasks for the maintainers of Carapacik/swagger_parser.
Improve the Health Facts of the GitHub repository Carapacik/swagger_parser. AwesomeRepos measures facts about how a repository is maintained, released, secured, and documented. Its page for this repository is https://awesomerepos.com/Carapacik/swagger_parser. A change to the repository can improve each of the 2 items below. Each item gives the measured fact or score, and a task. 1. A changelog file at the root Fact: No changelog file at the root (GitHub, 2026-11-13). Rule: The root of the default branch has a file named CHANGELOG, CHANGES, HISTORY, NEWS, RELEASE, or RELEASES, with no extension or with .md, .markdown, .rst, .txt, or .adoc. Release notes on GitHub releases do not count. Task: Add CHANGELOG.md at the root of the default branch. Write one section for each published release, newest first, from the GitHub releases, the Git tags, and the commit history. Do not invent changes. If the project uses a release tool (for example Changesets, release-please, or semantic-release), configure it to update this file for each release. 2. A code of conduct Fact: GitHub finds no code of conduct (GitHub, 2026-11-13). Rule: GitHub finds a code of conduct in the repository or in the owner's .github repository. Task: Add CODE_OF_CONDUCT.md at the root with the Contributor Covenant 2.1 text. Change only the contact method. Ask me for the contact; do not invent one. 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
Maintenance
3 of 4 checks-
Yes: Not archived
GitHub does not mark the repository as archived. Source
-
Yes: A push in the last 90 days
Last push on 2026-11-11, 1 day ago. Source
-
Yes: Commits in the last 13 weeks
20 commits on the default branch in the last 13 weeks (GitHub, 2026-11-13). Source
-
No: Commits in 26 or more of the last 52 weeks
Commits in 21 of the last 52 weeks (GitHub, 2026-11-13). Source
- 0
- 3
- 5
- 2
- 0
- 3
- 1
- 0
- 2
- 7
- 4
- 5
- 0
- 0
- 6
- 1
- 0
- 0
- 0
- 0
- 0
- 0
- 7
- 0
- 0
- 0
- 0
- 0
- 0
- 2
- 0
- 5
- 0
- 0
- 0
- 0
- 0
- 3
- 0
- 0
- 1
- 2
- 2
- 0
- 0
- 2
- 0
- 0
- 0
- 0
- 4
- 9
Releases
2 of 3 checksSecurity practice
1 of 1 check-
Yes: A security policy
GitHub finds a security policy (GitHub, 2026-11-13). Source
OpenSSF Scorecard has no result for this repository from the last 90 days.
Community files
2 of 3 checksObservations
Latest Observation, Nov 13, 2026: 307 stars, 110 forks, last push Nov 11, 2026, not archived. One of 2 Observations since Nov 12, 2026.