---
id: capability.security.repository-secret-prevention
owner: repo-manager
status: draft
domain: infotech
maturity:
  discovery:
    current: D3
    target: D5
    confidence: medium
    rationale: Owner scope, neighboring responsibilities, concrete use cases and limitations
      are documented; no exhaustive or generalized maturity claim.
  availability:
    current: A2
    target: A2
    confidence: medium
    rationale: 'Source interface assessed 2026-10-14: Repository observation plus
      pinned staged-blob scanner and hook integration. Availability describes the
      delivery form, not production acceptance. Local hooks are bypassable; coverage
      is exact-checkout scoped.'
external_evidence:
  completeness:
    level: C1
    confidence: low
    basis: Source artifacts establish a bounded capability; no independent consumer-completeness
      assessment in this review.
  reliability:
    level: R0
    confidence: low
    basis: No longitudinal consumer reliability measurement established by this review.
name: Repository metadata and staged-secret prevention
summary: Repository observation plus pinned staged-blob scanner and hook integration.
tags:
- security
- netkingdom
- framework-reuse
discovery:
  intent: Repository observation plus pinned staged-blob scanner and hook integration
  includes:
  - Repository observation plus pinned staged-blob scanner and hook integration
  excludes:
  - Local hooks are bypassable; coverage is exact-checkout scoped
  use_cases:
  - 'U07: Owner inventories, rotates, revokes and detects exposure of credentials'
  - 'U12: Developer builds and publishes through controlled source, dependency and
    runner paths'
availability:
  current_level: A2
  target_level: A2
  current_artifacts:
  - SCOPE.md
  - README.md
  consumption_modes:
  - CLI
  - source
relations:
  related_to:
  - capability.railiance.forge-infrastructure
  - capability.infotech.sbom-management
  - capability.statehub.workstream-coordinate
evidence:
  documentation:
  - SCOPE.md
  - README.md
consumer_guidance:
  recommended_for:
  - Owner inventories, rotates, revokes and detects exposure of credentials
  - Developer builds and publishes through controlled source, dependency and runner
    paths
  not_recommended_for:
  - Local hooks are bypassable; coverage is exact-checkout scoped
  known_limitations:
  - Local hooks are bypassable; coverage is exact-checkout scoped
  - 2026-10-14 architecture review estimates operational maturity separately; a registry
    entry does not authorize execution or establish deployment.
---

# Repository metadata and staged-secret prevention

Repository observation plus pinned staged-blob scanner and hook integration.

## Reuse boundary

Local hooks are bypassable; coverage is exact-checkout scoped.

## Supported use cases

- U07: Owner inventories, rotates, revokes and detects exposure of credentials
- U12: Developer builds and publishes through controlled source, dependency and runner paths

## Evidence and integration

- [SCOPE.md](../../SCOPE.md)
- [README.md](../../README.md)

Assessment: CUST-WP-0081, 2026-10-14. Relations identify interfaces to compose; they do not certify native integration. Existing external evidence levels are retained where present. New entries use conservative C1/R0 until consumer assessment exists.