WardenKit
Menu

Documentation

WardenKit documentation

Each WardenKit SDK ships with a quickstart, a usage reference, an explicit list of error states and activation instructions. Product-specific quickstarts and references are published here alongside each WardenKit product.

Security and Assurance

Open-Source Licence Policy SDK

Open-source licence policy as code. Turn your licence policy into an enforceable build rule: validate SPDX licence evidence locally and fail CI when a component breaks your policy.

npm install @wardenkit/open-source-licence-policy

Node.js 22.x · Node.js 24.x

Quickstart, usage and activation →

Conventions used across WardenKit SDKs

  • Results are returned as discriminated unions: check result.ok before reading result.value.
  • Dates that affect a rule outcome are always explicit parameters, never taken from the system clock.
  • Unsupported or malformed input produces a typed error state instead of a best guess.
  • Where a product evaluates against published rules, each rule profile is versioned, effective-dated and carries provenance to its official source.
  • Each SDK documents its own runtime, topology, network behaviour and data boundary on its own pages.

Deterministic tooling, professional judgment

WardenKit outputs are deterministic, inspectable technical results evaluated against the profile version and inputs you select. WardenKit provides developer tooling for evaluating and implementing compliance logic; it does not replace professional legal, tax, or accounting judgment. Selecting the applicable requirements, reviewing results and deciding what your organisation does remain with you and your advisers.

Something missing or unclear? Email support@wardenkit.com.