Repository navigation
v0.3.0
[0.3.0] - 2026-05-26
Supply chain integrity: registries can now ship per-file SHA256 checksums,
skill consumers can pin a version, and every install is recorded in a
forgent.lock.json that a new forgent verify command re-checks.
Added
- SHA256 file verification. Manifests may declare
files[].sha256
(lowercase hex). When present, forgent verifies the fetched body matches
before writing — a mismatch aborts the install with both hashes in the
error. When absent, forgent emits a one-timeWARNper skill and proceeds. --strict-sha256flag (andFORGENT_STRICT_SHA256=1env var) to refuse
any install whose manifest entry omits a sha256. For orgs that want to
enforce integrity across all registries.skill@versionsyntax.forgent add foo@1.2.3pins to that exact
version. The registry must declareitems[].version; otherwise the
install errors with a clear message ("registry X@Y does not declare a
version for skill 'foo'; remove the @1.2.3 pin or upgrade the registry").
Without a pin, behavior is unchanged.forgent.lock.json. Every successfuladdrecords the installed
skill's provider, source registry name+version, resolved skill version,
and per-file sha256 in a lockfile next toforgent.config.json. Commit
it to your repo for reproducible installs.forgent removedeletes the
matching entry.--dry-runskips the write.forgent verifycommand. Re-hashes installed files against
forgent.lock.jsonand reportsOK/FAILper file. Exits 1 on any
mismatch or missing file. No network — local-only check.- Each provider exports a
targetPath(installDir, skillName)helper used
byverifyto locate installed files without re-implementing per-provider
install conventions. - JSON Schema:
$defs/fileacceptssha256(64-char lowercase hex);
$defs/item.versionreservation is now validated at runtime via
assertOptionalSemver(was schema-only in 0.2.0).
Changed
loadRegistrynow rejects manifests whoseitems[].versionis not a
semver string and whosefiles[].sha256is not a 64-char hex string.- README has a new "Integrity & lockfile" section and the "What this is
not" disclaimer no longer claims forgent ships without a lockfile.
Notes
- Registries without sha256 still install (with WARN). The plan is to flip
the default in 1.0; until then, registries can roll out sha256
progressively. Pinning toforgent@0.3.0in agent-skill CI is recommended. - fs-mode (
--registry <local-path>) skips per-file fetch verification.
Whole-directory copy doesn't iterate per-manifest-file. The lockfile is
still written andverifystill works against the installed files. - Lockfile entries are sorted by skill name, files within each entry sorted
by path — for stable diffs when committed.