Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
@neilbmclaughlin/github-secrets
Advanced tools
A CLI utility to populate github secrets from a line based text file or stream
Note: version 2.0.0 is a breaking change and no longer works by default with .env format files. See examples below on how to do this in a unix environment
npm install -g @neilbmclaughlin/github-secrets
❯ github-secrets --help
github-secrets <cmd> [options]
Commands:
github-secrets put [filename] upsert repository secrets from either a file or stdin
github-secrets delete [filename] delete repository secrets from either a file or stdin
Options:
--help Show help [boolean]
--version Show version number [boolean]
Examples:
Put secrets from a file of space separated name-value pairs:
github-secrets put -a {token} -o {owner} -r {repo} test/data/env2
Put a single secret:
echo "foo bar" | github-secrets put -a {token} -o {owner} -r {repo}
Put secrets from an .env format file with comments filtered out:
egrep -v '^[ ]*#' test/data/env | github-secrets put -a {token} -o {owner} -r {repo} -s= test/data/env
Delete secrets from a file:
cut -f1 -d' ' test/data/env2 | github-secrets delete -a {access} -o {owner} -r {repo}
Put secrets from a URL (which should not be public!):
curl -s https://raw.githubusercontent.com/neilbmclaughlin/github-secrets/main/test/data/env2 | github-secrets put -a {token} -o {owner} -r {repo}
Options can also be specified in env vars prepended with 'GITHUB_SECRETS' (e.g. GITHUB_SECRETS_ACCESS_TOKEN, GITHUB_SECRETS_OWNER)
❯ github-secrets put --help
github-secrets put [filename]
upsert repository secrets from either a file or stdin
Options:
--help Show help [boolean]
--version Show version number [boolean]
-s, --separator key-value pair separator [default: " "]
-a, --access-token Github personal access token [required]
-o, --owner Github repository owner (defaults to access token owner)
-r, --repository Github repository
❯
❯ github-secrets delete --help
github-secrets delete [filename]
delete repository secrets from either a file or stdin
Options:
--help Show help [boolean]
--version Show version number [boolean]
-a, --access-token Github personal access token [required]
-o, --owner Github repository owner (defaults to access token owner)
-r, --repository Github repository
FAQs
manage git repository secrets
The npm package @neilbmclaughlin/github-secrets receives a total of 1 weekly downloads. As such, @neilbmclaughlin/github-secrets popularity was classified as not popular.
We found that @neilbmclaughlin/github-secrets 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
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.