@7shifts/teamsjson
Advanced tools
Describe your repository ownership with teams.json. Configure your teams, contexts, and let teams.json generate common configuration files for you.
Every teams.json has a "teams" property that describes the teams in your repository. Teams own things. Our opinion
is that teams own contexts, folders, or files.
Tests can be executed with npm test. There are test and fixtures in ./tests directory.
Run a build with npm run build.
Running teams can be done with npm run teams.
teams.json ships with some plugins ready to go. You can list all detected plugins with plugins:list.
codeowners plugin will generate your CODEOWNERS file for you."plugins" directive in teams.json can point
to any other plugin file and be run. (E.g. datadog output, or argo workflow generators)FAQs
Team ownership
We found that @7shifts/teamsjson demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 10 open source maintainers 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
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.
Product
Socket now supports uv.lock files to ensure consistent, secure dependency resolution for Python projects and enhance supply chain security.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.