Getting Started
Use this path for predictable adoption:
- baseline policy checks,
- provider-specific presets,
- optional strict hardening.
If you are new, read Overview first and keep Presets open while configuring.
1) Installâ
npm install --save-dev eslint-plugin-repo typescript
2) Enable baseline coverageâ
import repoPlugin from "eslint-plugin-repo";
export default [repoPlugin.configs.recommended];
recommended gives you repository baseline policy checks. See
recommended preset details.
Common first rules you will see from this baseline include
require-readme-file,
require-license-file, and
require-security-policy-file.
3) Add the provider preset you actually useâ
- Dependabot:
repoPlugin.configs.dependabot - GitHub:
repoPlugin.configs.github - GitLab:
repoPlugin.configs.gitlab - Bitbucket:
repoPlugin.configs.bitbucket - Codeberg / Forgejo:
repoPlugin.configs.codeberg - AWS:
repoPlugin.configs.aws - Azure:
repoPlugin.configs.azure - Google Cloud:
repoPlugin.configs.googleCloud - Docker:
repoPlugin.configs.docker - Vercel:
repoPlugin.configs.vercel - Netlify:
repoPlugin.configs.netlify - DigitalOcean:
repoPlugin.configs.DigitalOcean - Node:
repoPlugin.configs.node - AI guidance:
repoPlugin.configs.ai
Example layering:
import repoPlugin from "eslint-plugin-repo";
export default [
repoPlugin.configs.recommended,
repoPlugin.configs.github,
];
4) Optional stricter profileâ
repoPlugin.configs.strict: adds stricter policy checks on top of baseline (details).repoPlugin.configs.all: enables all rules in the plugin (details).
5) Verify and exploreâ
- Browse the Preset rule matrix to see exactly which rules are enabled where.
- Use All preset as the complete rule inventory.
- Share Overview internally when onboarding teammates.
Next reads by scenarioâ
- GitHub repositories: GitHub preset
- GitLab repositories: GitLab preset
- Cross-provider hardening: Strict preset
- AI policy files in repo root: AI preset