chore(backlog): add six awesome-nu plugin candidates
Merged
TO
8h ago+172+172+012345678901234567890123456789-4-4-0123456789
Refreshes the plugin backlog from the awesome-nu audit (2026-10-31). The audit previously showed 6 untracked plugins from awesome-nu's Plugins section; all 6 are now recorded, and the audit runs clean (33 in registry, 2 in manifest, 43 in backlog, 0 untracked).
New entries:
- wangjiawen2013/charton (nu_plugin_charton): ELIGIBLE. 448 stars. Plugin crate 0.9.0 pins nu-plugin =0.116; the v0.9.0 GitHub release has no assets, so intake is a CI build from source. Apache-2.0.
- kazu/seekzstdsep (nu_plugin_zstdsep): SOURCE_ONLY. Tag v0.9.0 with no release object; crate pins nu-plugin 0.116. MIT.
- gtnebel/nu_plugin_nuplot: ELIGIBLE with a caveat recorded in its note. It is implemented in Go (ainvaltin/nu-plugin library), so it does not fit the Cargo CI-build path; intake would ship the upstream release assets (v0.2.8 has 8) or need a Go build lane, and protocol compatibility needs a live check against current Nu. BSD-2-Clause.
- nushell core crates nu_plugin_gstat, nu_plugin_inc, nu_plugin_query: recorded as BUILTIN, following the existing nu_plugin_formats precedent, so the audit stops flagging them.
Data-only change; entries were verified against the upstream repos (crate pins, tags, release assets, licenses) before listing.
Summary by cubic
Adds six plugin candidates from the awesome-nu audit (2026-10-31) so the backlog stops flagging them as untracked, and promotes nu_plugin_charton 0.9.0 to the CI build farm.
- Records
nu_plugin_zstdsepas a new SOURCE_ONLY candidate; it pinsnu-plugin0.116 and needs a CI build from source since its tag has no release assets. - Records
nu_plugin_nuplotwith a caveat: it is a Go plugin, so it does not fit the Cargo CI-build path and protocol compatibility needs a live check. - Records
nu_plugin_gstat,nu_plugin_inc, andnu_plugin_queryasBUILTINsince they ship with Nu, following the existingnu_plugin_formatsprecedent.
New Features
- Promotes
nu_plugin_charton0.9.0 to the active manifest (now 34 plugins); its release has no assets, so it will be CI-built from source. - Builds workspace-member plugins: the manifest accepts an optional
cargo_packagefield that the build workflow passes ascargo build --package, covered by validation and tests.
Summary by CodeRabbit
- Documentation
- Added six plugin entries to the backlog, including their release and version details.
- The entries note compatibility and intake considerations and identify each plugin’s current status.