github-clone
Advanced tools
clone github repositories to the local box.
you can just npm install github-clone -g and then github-clone --directory <dir> --access_token <token>.
this installs an alias to the command into the system's path, meaning you can run github-clone from anywhere.
you can use a json or yaml configuration file (and call github-clone --config path/to/config)
{
directory: "path/to/clone/into",
repositories: {
type: "public",
sort: "updated"
},
access_token: "token"
}
the repositories object contains a type and a sort, as defined by the github repo. the directory key specifies a path to the directory in wich we wanna clone all your repositories. the access_token key specifies a personal access token from here.
you can use cron or scheduled tasks to make this happen at a regular interval, which is good fun.
FAQs
clone github repositories to the local box.
We found that github-clone 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.
Research
A supply chain attack on Axios introduced a malicious dependency, plain-crypto-js@4.2.1, published minutes earlier and absent from the project’s GitHub releases.
Research
Malicious versions of the Telnyx Python SDK on PyPI delivered credential-stealing malware via a multi-stage supply chain attack.
Security News
TeamPCP is partnering with ransomware group Vect to turn open source supply chain attacks on tools like Trivy and LiteLLM into large-scale ransomware operations.