npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@aikdna/kdna

v0.14.0

Published

KDNA toolkit compatibility package. The kdna CLI binary has moved to @aikdna/kdna-cli — use npm install -g @aikdna/kdna-cli.

Downloads

258

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

code2mp4code2mp4

Keywords

kdnakdna-cliai-agentdomain-judgmentjudgment-assetkdna-core

Readme

@aikdna/kdna

Compatibility package for the KDNA command line tools.

KDNA Core is the official KDNA judgment-asset format and runtime loading contract. .kdna assets are created, inspected, packed, validated, planned, and loaded through the KDNA toolchain. Compatible Agent consumption ends in a Runtime Capsule; it does not decode container internals directly.

This package only preserves older executable names. New integrations should depend on @aikdna/kdna-core and install @aikdna/kdna-cli directly. KDNA has one current Asset Container and the compatibility package does not introduce a second format or runtime route.

kdna-validate is a compatibility alias for kdna validate and accepts both current packaged .kdna assets and authoring source directories. It delegates to @aikdna/kdna-cli; it does not use the removed source-only validator.

The compatibility install path is:

npm install -g @aikdna/kdna-cli

This package remains available so older installation instructions using @aikdna/kdna resolve to the current KDNA CLI.

Version 0.14.0 is bound to @aikdna/[email protected] and @aikdna/[email protected], requires Node.js 20 or later, and installs one physical Core package. It is a migration bridge, not the recommended package for new applications.

Current runtime path

The public runtime path starts from a packaged .kdna asset and delegates to the current CLI/Core contract.

Usage:

kdna pack      examples/minimal /tmp/out.kdna
kdna validate  /tmp/out.kdna
kdna plan-load /tmp/out.kdna
kdna load      /tmp/out.kdna --profile=compact --as=json

The local invocation in this monorepo is:

node packages/kdna/bin/kdna.js <command> <args>

Or via the npm scripts in the repo root:

npm run kdna:pack     -- examples/minimal /tmp/out.kdna
npm run kdna:validate -- /tmp/out.kdna

The runtime is content-neutral. Output never claims that an asset is "trusted", "recommended", "high_quality", or "officially approved". It reports format, schema, payload, checksums, and load-contract validity only. Format-valid does not mean content-good; that is a runtime policy decision owned by the caller.