nvim-rs safe for commercial use?Rust crate package · License: LGPL-3.0
nvim-rs is licensed under LGPL-3.0, which imposes no source-disclosure obligation in any of the shipping models below.
| How you ship it | Result | Why |
|---|---|---|
| Hosted SaaS | Needs review | LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review. |
| Distributed binary / app | Needs review | LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review. |
| Delivered to customer | Needs review | LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review. |
| Internal use only | Needs review | LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review. |
| Published library | Needs review | LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review. |
Source disclosureAttribution
If you only use it at build time, the answer changes.
LGPL-3.0 appears as a dev dependency, so it is not part of the artifact you ship. Distribution-triggered obligations do not arise. Tools that emit code into your output, such as code generators, are a separate case worth checking individually.
nvim-rs is licensed under LGPL-3.0, which imposes no source-disclosure obligation in any of the shipping models below.
LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review.
LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review.
LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review.
LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review.
LGPL-3.0 requires that recipients be able to replace the library with a modified version. Under static linking this normally means shipping object files or equivalent relinking material. Static linking was assumed here, so this case needs individual review.
LGPL-3.0 appears as a dev dependency, so it is not part of the artifact you ship. Distribution-triggered obligations do not arise. Tools that emit code into your output, such as code generators, are a separate case worth checking individually.
This page covers one package. Your Cargo.lock has many more.
Check your whole manifest →The license was read from crates.io, then evaluated against each shipping model. Dependencies in this ecosystem are linked statically, which is assumed here. Only the declared license is considered; code copied into a project's own source files is not detected by this method.
License data last reviewed .
LicenseGuard reports information derived from published license texts and dependency manifests. It is not legal advice and using it does not create an attorney-client relationship. Results reflect license metadata as declared; they do not identify every obligation or violation. Consult qualified counsel for decisions that matter.
Listed in the official MCP registry, on Glama and on Smithery. Source on GitHub (Apache-2.0).