lazy_static
Cargov1.5.0A macro for declaring lazily evaluated statics in Rust.
Not recommended for new projects
No — lazy_static should not be adopted for new projects. Last published 810 days ago. 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.
- DMaintenance: grade D, Poor — a real concern.
Last published 810 days ago.
- AWeight: grade A, Excellent.
Zero runtime dependencies.
- ASupply chain: grade A, Excellent.
No install scripts, 2 maintainers, and a contained dependency surface.
- 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 lazy_static 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
lazy_static 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 |
|---|---|---|---|---|
| lazy_staticthis page | 0 | 0 | — | 2 years ago |
| once_cell | 0 | 0 | — | 1 day ago |
Release history
No releases in the last two years, typically about 47 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 1.5.0latest | 2 years ago | — | MIT OR Apache-2.0 |
| 1.1.1 | 6 years ago | — | MIT/Apache-2.0 |
| 1.4.0 | 7 years ago | — | MIT/Apache-2.0 |
| 1.3.0 | 7 years ago | — | MIT/Apache-2.0 |
| 1.2.0 | 7 years ago | — | MIT/Apache-2.0 |
| 1.1.0 | 8 years ago | — | MIT/Apache-2.0 |
| 1.0.2 | 8 years ago | — | MIT/Apache-2.0 |
| 1.0.1 | 8 years ago | — | MIT/Apache-2.0 |
| 1.0.0 | 8 years ago | — | MIT/Apache-2.0 |
| 0.2.11 | 8 years ago | — | MIT/Apache-2.0 |
| 0.2.10 | 8 years ago | — | MIT/Apache-2.0 |
| 0.2.9 | 9 years ago | — | MIT/Apache-2.0 |
| 0.2.8 | 9 years ago | — | MIT/Apache-2.0 |
| 0.2.7 | 9 years ago | — | MIT/Apache-2.0 |
| 0.2.6 | 9 years ago | — | MIT |
Overview
lazy_static is an Cargo package that a macro for declaring lazily evaluated statics in Rust. The latest version is 1.5.0.
Who should use it
Teams working in the Cargo ecosystem who need a macro for declaring lazily evaluated statics in Rust 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 lazy_static?
No — lazy_static should not be adopted for new projects. Last published 810 days ago. No license declared — you have no explicit right to use this code.
How do I install lazy_static?
Run `cargo add lazy_static` to add lazy_static to your Cargo project.
What license is lazy_static released under?
No license was detected in lazy_static's metadata; review the repository before use.
Is lazy_static still maintained?
The most recent release of lazy_static (v1.5.0) was published 2 years ago.