Package LICENSE file
Keep the proprietary LICENSE with distributions and align install docs with your plan.
What you will learn
- Locate the package LICENSE
- Follow Install + Pricing for access
- Keep LICENSE with redistributed artifacts you are allowed to ship
Prerequisites
Surface
| Imports | @tmrxjd/agent-governance-system |
|---|---|
| Config | LICENSE · package.json#license |
What this feature does
The package ships a proprietary LICENSE. Install from the registry using `/docs/install-commercial/`, then unlock tiers with `AGS_LICENSE_KEY` from Pricing/Checkout. Do not strip LICENSE from any allowed redistribution.
Configuration
Primary surfaces: LICENSE at package root, package.json license field, AGS_LICENSE_KEY for product entitlements.
{
"license": "UNLICENSED",
"private": true
}How to call it
Use these package entrypoints from host or agent code: @tmrxjd/agent-governance-system.. Prefer the documented export path over deep relative imports.
- Read /docs/licensing/
- Install via /docs/install-commercial/
- Retain LICENSE in publish
- sentinel_status / license checks
import { createPluginHost } from '@tmrxjd/agent-governance-system/plugin'
import { enforceLicense } from '@tmrxjd/agent-governance-system'
const host = createPluginHost({ repoRoot })
const report = enforceLicense(host.ctx)
if (!report.ok) console.error(report.issues, report.nextActions)What success looks like
LICENSE present in published tarball
Install docs match your plan
Sentinel license reflex quiet
Common failure modes
Stripping LICENSE files from redistrib
Sharing registry tokens outside your org
Mixing license obligations across forks