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.
@envsa/repo-config
Advanced tools
Repository configuration and GitHub workflows for @envsa/shared-config.
Repository configuration and GitHub workflows for @envsa/shared-config.
It's a pnpm
-flavored shared config with some essential files for a fresh repo.
This includes the following:
.npmrc
with hoisting patterns for shared-config
tool access.gitignore
with typical patterns.vscode
extension recommendations (additional settings and recommendations come from other shared-config
packages).github
folder with workflows:
github-release.yml
Automates turning turning vX.X.X tags on main into GitHub releases with changelogssync-metadata.yml
Populates GitHub repo metadata from package.jsonIn order to work around some hoisting issues related to plugin resolution in the other @envsa/shared-config
packages, it's critical that it is applied before any other @envsa/shared-config
packages are installed.
See @envsa/shared-config
for the recommended single-package approach.
If you just need to set up your .npmrc
in anticipation of installing another shared config, you can run the script via dlx
to copy the .npmrc
to your home folder:
pnpm dlx @envsa/repo-config --init
Optionally, you can install the package if you think you'll ever want to regenerate the repo config files.
Add the package:
pnpm add -D @envsa/repo-config
If / when you need to regenerate the repo config files, you can run the bundled script:
pnpm exec repo-config --init
There are two options for authenticating the release workflow action:
If you want releases to come from your account instead of github_actions
, then:
Create a fine-grained personal access token in your GitHub account with the following permissions:
Permission | Access |
---|---|
Administration | Read and write |
Contents | Read and write |
Metadata | Read-only |
Add the token as a secret to the repository under the key PERSONAL_ACCESS_TOKEN
.
Note: Action dependencies have been forked.
repo-config
Repository configuration and GitHub workflows for @envsa/shared-config.
Usage:
repo-config [<file|glob> ...]
Option | Argument | Description |
---|---|---|
--init -i | Initialize by copying starter config files to your project root. | |
--print-config -p | <path> | Print the effective configuration at a certain path. |
--help -h | Print this help info. | |
--version -v | Print the package version. |
Eric Mika is the author of the original @kitschpatrol/shared-config project on which this is based.
MIT © Liam Rella
FAQs
Repository configuration and GitHub workflows for @envsa/shared-config.
The npm package @envsa/repo-config receives a total of 36 weekly downloads. As such, @envsa/repo-config popularity was classified as not popular.
We found that @envsa/repo-config demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 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
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.