Kanject.Cli
1.5.1
Prefix Reserved
See the version list below for details.
dotnet tool install --global Kanject.Cli --version 1.5.1
dotnet new tool-manifest
dotnet tool install --local Kanject.Cli --version 1.5.1
#tool dotnet:?package=Kanject.Cli&version=1.5.1
nuke :add-package Kanject.Cli --version 1.5.1
Kanject.Cli
A single .NET global tool that drives C# AWS services from dotnet new to
kanject aws deploy --env prod — wrapping the existing dotnet/AWS toolchain so
your inner loop stays vanilla and the Lambda, ECS Fargate, static-site, and
coupled full-stack deploy plumbing disappears behind one committed manifest.
Install
dotnet tool install --global Kanject.Cli
Requires the .NET 10 SDK. The aws, msbuild, and github providers ship
in the box — no extra installs.
Choose a workflow
- Deploy applications: Lambda, ECS Fargate, or a coupled SPA/backend. Choose independent service roots, a shared multi-Lambda stack, or a coordinated frontend/backend pair.
- Publish libraries:
kanject packages init, thenkanject packages planandkanject packages verifyfrom the package repository root. - Distribute desktop apps: initialize the product manifest, register with
kanject add distributable, and configure delivery destinations.
Start at Getting started for workflow selection. Service commands run from the directory containing that service's manifest, which can differ from the repository or solution root. The current static-site shape requires a coupled backend.
Discover commands with kanject --help and kanject aws --help.
What it does
- Bootstrap —
kanject newscaffolds a project from a bundled template and initializes it;kanject initadds the manifest, stage files and lock file to an existing project. - Deploy —
kanject aws deploy --env <stage>resolves cross-repo dependencies and env, builds the provider artifacts, and ships the manifest's target (Lambda, ECS Fargate, static site, or a coupled backend + site), recording every release in an S3 deployment ledger. - Rollback —
kanject aws rollback --env prodshows the last 10 deployments with dates, statuses, targets, and commit summaries; pick one and Kanject does the target-native promotion with the prior artifact still immutable in S3/ECR. - And more — cross-repo dependency sync, a local test runner, env/param/secret
management, static-site previews and ephemeral backend previews
(
kanject aws deploy --preview <NAME>), DynamoDB change feeds, a managed streaming Function URL and CloudFront edge, VPC & custom-domain wiring, multi-function services, AWS-native pipeline scaffolding, NuGet package publishing, desktop distribution, and sign-in for paid Kanject packages (kanject login,kanject add package).
It invokes — never replaces — dotnet new, dotnet build, and dotnet lambda, and drives AWS services through their SDK APIs (including
CloudFormation change sets). The dotnet-native experience stays; kanject only
owns the AWS plumbing that doesn't have a great answer in the box.
Learn more
- Getting started: kanject.com/docs/getting-started
- Website: kanject.com/cli
- In-tool help:
kanject --help,kanject aws --help
License
Commercial — governed by the Kanject Code Libraries License Agreement (KCLLA);
see the bundled LICENSE.md. © Kanject Business Solutions.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.5.0 | 109 | 11/16/2026 |
| 2.4.0 | 95 | 11/16/2026 |
| 2.3.0 | 118 | 11/15/2026 |
| 2.2.0 | 138 | 11/14/2026 |
| 2.1.0 | 99 | 11/13/2026 |
| 2.0.2 | 107 | 11/13/2026 |
| 2.0.1 | 99 | 11/13/2026 |
| 2.0.0 | 105 | 11/12/2026 |
| 1.5.1 | 127 | 11/11/2026 |
| 1.5.0 | 125 | 11/10/2026 |
| 1.4.0 | 110 | 11/4/2026 |
| 1.3.0 | 123 | 11/2/2026 |
| 1.2.0 | 161 | 11/1/2026 |
| 1.1.0 | 119 | 11/1/2026 |
| 1.0.79 | 115 | 10/30/2026 |
| 1.0.78 | 105 | 10/30/2026 |
| 1.0.77 | 112 | 10/29/2026 |
| 1.0.76 | 106 | 10/29/2026 |
| 1.0.75 | 104 | 10/29/2026 |
| 1.0.74 | 106 | 10/28/2026 |
- `kanject aws pipeline up --add-region` keeps a schema-2 stage file at schema 2.
It rewrote the file as stage schema 1: `profile`, `stack`, `artifactBucket` and the other AWS settings moved from the `aws` block back to the top level, and `provider` was dropped. No setting was lost and the file still loaded, but it no longer matched the layout `kanject init` writes, and `kanject doctor` then suggested `kanject migrate --schema-v3` (`KANCLI760`) for a project that had never left it. The command now saves the stage the way every other command does, at the file's own version and with its `provider`: an existing target keeps its settings under `targets[].aws`, and a schema-1 file stays schema 1. To repair a file an earlier version rewrote, run `kanject migrate --schema-v3`.
- `kanject doctor` reports a schema-3 manifest as `(schema v3)`.
The manifest row read `kanject-cli/manifest.json (schema v2)` for the manifest `kanject init` and `kanject new` have written since 1.2.0, in the table and in the `message` of `--json`. The JSON shape is unchanged.
- `kanject init --help` says what `--schema 2` writes.
The option's description names the provider-neutral layout (manifest schema 3, stage schema 2) and the legacy one `--schema 1` keeps. When no Lambda project is found and `init` falls back to schema 1, the line it prints now points at `kanject migrate --schema-v3`, the upgrade that reaches that layout, instead of `--schema-v2`.
- The AWS provider ships a patched `System.Formats.Cbor`.
The copy under `providers/aws/` moves from 9.0.5 to 10.0.15, which fixes GHSA-vmv3-wvjp-wqpj (CVE-2026-118747, moderate): CBOR map keys chosen to collide could make the library's duplicate-key check slow enough to deny service. The CLI reads CBOR only in responses from CloudWatch and CodeConnections. No command, flag, output or diagnostic changes.
- The advisory covers `System.Formats.Cbor` 9.0.x below 9.0.24 and 10.0.x below 10.0.15. The CLI never referenced the package itself: `AWSSDK.Extensions.CborProtocol` asks for 9.0.5, and no AWS SDK release asks for a patched version yet, so the AWS provider now references it directly.
- 10.0.15 rather than 9.0.24 because the 9.0 line went out of support on 2026-11-10.
- The repository's NuGet audit gate reports the advisory as a build error (`NU1902`), so `main` could not be built or released until this landed.