Our take
Activeregular commits- Activity
- 36
- Community
- 74
- Issues
- 21
- Pull requests
- 67
+0 stars in the last 30 days
webargs is an actively maintained, MIT-licensed option for marshmallow-based request parsing across several Python frameworks, with recent commits and merged pull requests but no release in the past year.
Good fit if
- Your application uses one of the supported frameworks and needs to parse and validate HTTP request arguments.
- You already use marshmallow and want its fields and validation in request handling.
- You want a project with ongoing development, a broad contributor base, and an MIT license.
Look elsewhere if
- Your framework is not among the listed integrations or you need a different request-validation model.
- Your deployment must rely on a release published within the past year.
All health signals
| Last commit | 2026-10-13 (3 days ago) |
|---|---|
| Commits, last 90 days | 17 |
| Releases, last 12 months | 0 |
| Contributors | 63 (top contributor: 42% of commits) |
| Issues closed, last 90 days | 0 |
| Pull requests merged, last 90 days | 16 (typically merged in 0 days) |
| Project age | 12 years |
Checked on 2026-10-17 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
1,411Forks
175Change since Nov 16, 2026: 0 stars·0 forks
Overview
webargs is a Python library built on marshmallow for parsing and validating HTTP request objects. It addresses the repetitive work of extracting and validating incoming arguments, with integrations for Flask, Django, Bottle, Tornado, Pyramid, Falcon, and aiohttp.
It is intended for developers building HTTP APIs or web applications who want request parsing to work with their existing framework and marshmallow schemas or fields. The project supports Python 3.10 and later.
Key Features
- Parse arguments from HTTP requests and validate them against field definitions.
- Integrate request parsing with Flask, Django, Bottle, Tornado, Pyramid, Falcon, and aiohttp.
- Use decorators such as
use_argsto pass parsed arguments into a handler. - Select a request location, such as query parameters, when applying parsing to a route.
- Work with marshmallow 3 and 4, according to the project README.
- Install as a Python package with pip.
Use Cases
- A Flask API developer can validate query parameters before a route handler uses them.
- A team maintaining endpoints across supported frameworks can use a common request-parsing approach.
- Developers using marshmallow can apply its field-based validation to incoming HTTP arguments.
- A web application team can make request validation part of handler integration rather than repeating parsing logic in each handler.
What you need
Detected in the repository
- Python >=3.10 (from pyproject.toml)
- A test suite and automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Install the package:
pip install -U webargs
See the README and documentation for framework-specific usage.
Alternatives
- fastapi: FastAPI validates request data as part of a full API framework, while webargs adds parsing and validation to existing web frameworks.
- flask-restful: Flask-RESTful structures Flask applications as REST APIs and includes request parsing, while webargs focuses on parsing across multiple frameworks.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| webargs | Python | MIT | 1.4k | Active |
| fastapi | Python | MIT | 103k | Active |
| flask-restful | Python | BSD-3-Clause | 6.9k | Inactive |
Considerations
The project is actively developed, but its measured release history shows no releases in the past year, so teams with release-cadence requirements should check the latest package and changelog before adopting it. It requires Python 3.10 or later. The MIT license is permissive; review the license for its terms. The README describes framework integrations and parsing and validation, but does not claim support for frameworks beyond those listed.
Found this useful?
Share it with someone who would like webargs.