ce-notebook-audit

You can audit notebooks for private API usage and policy violations by scanning the notebooks/ directory to detect private-member access, restricted imports, and rendering errors. The tool enforces detection rules defined in ADR-012 and generates actionable compliance reports.

Notebook policy compliance checking scans notebooks for private-member access, restricted imports, and rendering errors. You need it for data science teams and educational workloads to enforce public-API correctness and verify agent instruction consistency across CI and local environments.

To check agent instruction file consistency in CI pipelines, run the notebook audit workflow which validates agent instructions and executes navigation tests. This verifies rendering and instruction compliance to ensure no restricted imports or private-member usage violations exist.

Yes, notebook auditing is explicitly applicable to data science teams and educational workloads. It scans notebooks for private-member access, restricted imports, and rendering errors across both CI and local environments to enforce policy compliance and public-API correctness.

The best way to scan notebooks for restricted imports and rendering errors is to run the notebook audit workflow. It enforces detection rules from ADR-012 and related ADRs, validates instruction consistency, and produces actionable audit reports detailing all violations.

Your notebook audit report shows private-member usage violations because the scanner detected code accessing non-public APIs. The audit enforces ADR-012 detection rules to identify private-member access, restricted imports, and rendering errors across your notebooks/ directory.