nom
Cargov8.0.0A byte-oriented, zero-copy, parser combinators library
Not recommended for new projects
No — nom should not be adopted for new projects. Last published 591 days ago. 2 releases in the last 2 years. No license declared — you have no explicit right to use this code.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- CMaintenance: grade C, Fair — worth a look.
Last published 591 days ago. 2 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- BSupply chain: grade B, Good.
This package has a single maintainer (bus factor of 1).
- FLicense: grade F, Failing.
No license declared — you have no explicit right to use this code.
Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.
Install cost
What you actually take on by adding nom to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Rust edition
- No constraint declared
nom vs the alternatives
Packages solving a similar problem in the cargo ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| nomthis page | 0 | 0 | — | 1 year ago |
| clap | 0 | 0 | — | 1 day ago |
Release history
2 releases in the last two years, typically about 43 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 8.0.0latest | 1 year ago | — | MIT |
| 8.0.0-beta.1 | 1 year ago | — | MIT |
| 8.0.0-alpha2 | 2 years ago | — | MIT |
| 8.0.0-alpha1 | 2 years ago | — | MIT |
| 6.2.2 | 3 years ago | — | MIT |
| 5.1.3 | 3 years ago | — | MIT |
| 7.1.3 | 3 years ago | — | MIT |
| 7.1.2 | 3 years ago | — | MIT |
| 7.1.1 | 4 years ago | — | MIT |
| 7.1.0 | 4 years ago | — | MIT |
| 7.0.0 | 5 years ago | — | MIT |
| 7.0.0-alpha3 | 5 years ago | — | MIT |
| 7.0.0-alpha2 | 5 years ago | — | MIT |
| 7.0.0-alpha1 | 5 years ago | — | MIT |
| 6.2.1 | 5 years ago | — | MIT |
Overview
nom is an Cargo package that a byte-oriented, zero-copy, parser combinators library. The latest version is 8.0.0.
Who should use it
Teams working in the Cargo ecosystem who need a byte-oriented, zero-copy, parser combinators library and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your Cargo stack.
Pros
- Zero runtime dependencies — minimal footprint.
Cons
- No license detected — review usage terms before adopting.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use nom?
No — nom should not be adopted for new projects. Last published 591 days ago. 2 releases in the last 2 years. No license declared — you have no explicit right to use this code.
How do I install nom?
Run `cargo add nom` to add nom to your Cargo project.
What license is nom released under?
No license was detected in nom's metadata; review the repository before use.
Is nom still maintained?
The most recent release of nom (v8.0.0) was published 1 year ago.