generate-codeowners
Advanced tools
[](https://www.npmjs.com/package/generate-codeowners)
Original use case was to introduce CODEOWNERS-files within an organization with a large amount of repositories. The idea was to generate a file based on the Git-history.
Usage: generate-codeowners [options]
Options:
-gd, --gitdir <dir> Directory with Git repository. (default: "generate-codeowners")
-ii, --ignoreidentifiers <regexp> Directory with Git repository. (default: ["noreply"])
-s, --since <time> Same as Git:s <since> format. (default: "365.day.ago")
-id, --identifier <committerEmailmail| Same as Git:s <since> format. (default: "committerEmailmail")
committerEmailUser|
committerName>
-cf, --codeownersfile <name> The CODEOWNERS-file (default: "CODEOWNERS")
-d, --dryrun Do not change anything, just print what would be changed. (default: false)
-v, --version Display version (default: false)
-h, --help display help for command
FAQs
[](https://www.npmjs.com/package/generate-codeowners)
We found that generate-codeowners demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.