# TrakHound PackageManager

> A package server for the TrakHound Framework that controls which Packages each Instance can install. Versions are checked for their signature, publisher, git provenance, and known vulnerabilities, approved through Development, Test, and Production channels, and reported on for every Instance. Licensed per server, for any number of Instances.

URL: https://www.trakhound.com/trakhound-package-manager

*Control Which Packages Run on Every Instance*

- One package server for your own applications, TrakHound Packages, and third-party Packages
- Instances register before they can install anything, and only see the Packages approved for them
- Every version is checked for its signature, publisher, git provenance, and known vulnerabilities
- Approve each version through Development, Test, and Production channels
- See what every Instance has installed, with drift detection and reports for IT
- Signed offline bundles carry Packages to sites without network access
- Runs on your own TrakHound Instance, on premise

[Coming Soon, Get Notified](https://www.trakhound.com/contact?product=trakhound-package-manager&type=info)[Licensing](https://www.trakhound.com/trakhound-package-manager#licensing) [Learn More](https://www.trakhound.com/trakhound-package-manager#review)

- Runs On Premise
- Works Offline
- TrakHound Framework

[Review & **Approval** Approve each version to a channel](https://www.trakhound.com/trakhound-package-manager#review) [Package **Checks** Signatures, git provenance, and vulnerabilities](https://www.trakhound.com/trakhound-package-manager#checks) [Instances & **Drift** What every Instance has installed](https://www.trakhound.com/trakhound-package-manager#instances) [Reports for **IT** Signed record copies and SBOMs](https://www.trakhound.com/trakhound-package-manager#reports)

*Decide What Reaches Production*

## Review & Approval

TrakHound PackageManager is a package server that you host on a TrakHound Instance. It becomes the only place your Instances get Packages from, whether they are your own applications, TrakHound Packages, or Packages from a vendor. Every version is checked and reviewed before an Instance can install it.

- **Channels** - Approve each version to Development, Test, and Production separately. A version must be approved in Test before Production, and each of its dependencies needs an approved version in the same channel
- **Review Queue** - Versions that pass their checks wait for a reviewer, who sees the provenance, check results, vulnerabilities, and dependencies before deciding
- **Separation of duties** - The person who uploaded a version can't approve it
- **Reject, Deprecate, and Revoke** - Each needs a reason. A revoked version can no longer be installed in that channel
- **Immutable versions** - A stored version never changes. A different build has to be published as a new version
- **Evidence** - Every decision keeps what the reviewer saw (content hash, signing key, check results, dependencies, and channels) and is recorded in the audit log
- **Upload from CI** - A build pipeline uploads with an API key, and each publisher lists the identities allowed to upload its Packages

[Development, Test & Production](https://www.trakhound.com/docs/trakhound-framework/environments)

*Know Who Built a Package, from What, and What It Contains*

## Package Checks

Each uploaded version is checked before it reaches the Review Queue, and stored versions are scanned again as new advisories are published. Each channel sets which findings block an approval, so Production can be stricter than Development.

- **Signature and publisher** - The Package must be signed by a key registered to a verified publisher, with an ID that starts with one of the publisher's prefixes and files that match its manifest
- **Publisher Registry** - Register publishers and their keys, and revoke a key that has been compromised so nothing it signed is accepted
- **Git provenance** - The repository, branch, commit, and builder recorded in the Package are checked against a repository allowlist and GitHub: that the commit exists, came from a clean working tree, is on an allowed branch, has its release tag, and was built by CI
- **Vulnerabilities** - The libraries in each Package's SBOM are scanned against OSV.dev, which includes the GitHub Advisory Database, and against internal advisories you enter yourself
- **Channel policy** - By default a Critical finding blocks approval to Production. A channel can also require an SBOM, and can revoke approved versions automatically when a new advisory is found
- **Waivers** - Accept the risk of an advisory with an owner, a reason, and an expiry within a year
- **Alerts** - New findings on Packages that are approved or installed are emailed, with where each one is approved and installed
- **No internet required** - Turn off the OSV.dev lookups to scan only against internal advisories on an isolated network

[Signing and Verification](https://www.trakhound.com/docs/trakhound-framework/packages#verification)

*See What Every Instance Has Installed*

## Instances & Drift

Each Instance is registered with a channel and given an access token, then added to the Package Manager as a normal Package source. Registered Instances report what they have installed, so IT has a current list of the Packages on every Instance.

- **Channel-filtered feed** - An Instance only sees the versions approved in its channel. Anything else looks as if it doesn't exist
- **Suspend or retire** - Stop an Instance from installing anything, move it to another channel, or issue a new token
- **Inventory** - Instances report their installed Packages at startup, after a change, and on a heartbeat, and each change is recorded
- **Drift** - Find Packages that were modified, copied onto an Instance by hand, not approved for its channel, revoked after they were installed, or behind the latest approved version
- **Enforcement** - Each Instance gets a signed list of the builds approved in its channel. In the `RequireApproval` verification mode, an Instance refuses any Package that isn't on it
- **Trusted publishers** - Instances trust the publishers the Package Manager verified, so their Packages show as Verified without adding each key by hand
- **Cut off from the server** - An Instance keeps running the Packages it has. It installs nothing new once its approval list expires (7 days by default)

[Connect an Instance](https://www.trakhound.com/docs/trakhound-framework/packages#package-manager)

*Records for IT, Quality, and Auditors*

## Reports

Reports answer the questions an audit asks: what is installed where, who approved it, and what changed. Each report opens as CSV or JSON.

- **Instance Packages** - The Packages installed on one Instance, with their checks, provenance, and drift
- **Fleet** - Where each version of a Package is installed across every Instance
- **Change Log** - Packages installed, removed, or changed on any Instance in a time range
- **Approval Register** - Every review decision, with who made it, why, and the build's content hash, key, and commit
- **Instance Register** - Every registered Instance with its site, owner, channel, state, and last report
- **Vulnerable Installs** - Open findings on the Packages that are installed, with the fixed version and any waiver
- **SBOM** - A CycloneDX SBOM for each Instance, listing its Packages, their libraries, and open findings
- **Record copies** - Keep a dated copy of a report with its SHA-256, signed with the server's key, so it can be shown later that the copy hasn't changed

*Bring In Packages from TrakHound, Vendors, and Other Sites*

## Upstream Sources & Offline Bundles

Packages you don't build yourself come in through the same checks as your own. A central Package Manager can also feed the Package Managers at each site.

- **Upstream sources** - Bring in new versions from TrakHound's package server, a vendor's, or another Package Manager, on demand or on a schedule
- **Preview** - A dry run lists what a sync would bring in without downloading anything
- **Auto-approve** - A source can approve its versions to the channels you choose, such as Development, with every rule of a review still applied
- **Offline bundles** - Export a channel's approved versions as a single signed file and import it at a site without network access
- **Trusted server keys** - A bundle is only imported when it's signed by a server key you trust and every file matches its hash. Each Package in it is then checked and reviewed as usual

*One License per Server, for Any Number of Instances*

## Licensing

TrakHound PackageManager is a licensed product. A license is issued for the server the Package Manager runs on, and registering an Instance never uses one, so every Instance can be registered and the inventory stays complete. A Package Manager at another site needs its own license.

- **Checked offline** - License Codes are signed and checked on your server, without contacting TrakHound
- **Expiry warnings** - Every page shows when the license expires within 30 days
- **Grace period** - For 14 days after a license expires, everything keeps working except registering new Instances
- **A lapsed license never stops a plant** - Registered Instances keep installing the versions already approved, reports stay available, and revocations still apply. Uploads, reviews, and new Instances wait for a license
- **Requirements** - A TrakHound Instance (0.15.1 or later) with a Tables Service and a Blobs Service. The Package Manager installs as three Packages: an API, an App, and a Function

Contact us for pricing. Licenses are requested and imported the same way as other TrakHound products.

[Get Notified](https://www.trakhound.com/contact?product=trakhound-package-manager&type=info)[Request Pricing](https://www.trakhound.com/contact?product=trakhound-package-manager&type=pricing) [Licensing Guide](https://www.trakhound.com/docs/licensing)
