Skip to content
targatetargate

targate

Interfaces

Section titled “Interfaces”
Interface Description
AiCachePolicy Shape of the aiCache section of targate.policy.* — all fields optional.
ApprovalRecord -
ArtifactSignal -
DependencyPolicy Team dependency policy — schema from the workshop proposal (§9 phase 6).
IndexedFile -
InstallPlan -
LockedPackageArtifact -
PackageFileIndex -
PlanPackageSpec -
PolicyFile Public entry point of the “targate” package: the types other tooling may import. Repository config itself is declarative (.yaml/.yml/.json) and parsed, never executed, so there are no runtime config helpers here.
RegistryPolicy Public entry point of the “targate” package: the types other tooling may import. Repository config itself is declarative (.yaml/.yml/.json) and parsed, never executed, so there are no runtime config helpers here.
ResolvedResourceLimits -
ResourceLimits Resource budgets applied to every untrusted network/package input.
RiskAssessment -
Signals -

Type Aliases

Section titled “Type Aliases”
Type Alias Description
ApprovalsMap Keyed by “name@version” — approvals are version-specific by design.
ArtifactTrust How strongly the analyzed tarball bytes are bound to an independent identity.
Decision -
RiskLevel -
ScriptPolicy -

Functions

Section titled “Functions”
Function Description
assertCompleteFileIndex A partial index must never be interpreted as a clean package analysis.
buildPackageFileIndex Traverse an extracted package once and retain only bounded file metadata. File contents stay on disk and are read lazily by the analyzers that need them, keeping the shared index useful even for large packages.