comply-human-passunchanged
Asserts — A repo that satisfies every rule: the clean verdict wording and exit 0.
Ran hermex comply in fixtures/repos/compliant → exit 0, as asserted
Config fixtures/repos/compliant/hermex.config.ts · Fixture fixtures/repos/compliant (overview) · Case comply-human-pass (dossier)
Reproduce locally: pnpm run test:output -- --filter comply-human-pass
fixtures/repos/compliant/hermex.config.ts
import type { HermexConfigInput } from '../../../src/config/types.ts';
/**
* Deliberately the same rule set as `fixtures/hermex.config.ts` — the only
* thing that differs is the repo underneath it. Keeping the rules identical
* is what makes the `comply-pass` / `comply-fail` pair a real contrast:
* every difference in their output comes from the repo, never from the
* policy. If a rule is added to the primary config, add it here too and
* satisfy it, or the pair stops proving anything.
*/
export default {
rules: {
'no-files': [
{
severity: 'error',
patterns: ['jest.config.*', '.babelrc'],
message: 'Use vitest + Vite',
},
],
'no-packages': [
{ severity: 'error', patterns: ['moment'], message: 'Use date-fns or dayjs' },
],
'require-files': [
{ severity: 'error', patterns: ['.nvmrc'] },
{ severity: 'warn', patterns: ['.editorconfig'] },
],
'require-packages': [
{
severity: 'error',
patterns: ['typescript'],
message: 'TypeScript is required',
},
],
'require-scripts': [
{
severity: 'error',
patterns: ['build', 'test'],
message: 'Required npm scripts',
},
],
'require-package-fields': [{ severity: 'warn', patterns: ['engines', 'license'] }],
'require-engine-version': { severity: 'warn', range: '>=20', message: 'Minimum Node 20 required' },
},
} satisfies HermexConfigInput;
stdout.txthermex v<version>
- Parsing lockfile...
✔ Found pnpm lockfile (supports: v5, v6, v9) - 2 packages
✔ Found 2 files
✔ Analysis complete! Analyzed 2/2 files
🟢 Compliant
stderr.txt