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.
make-coverage-badge
Advanced tools
Create a coverage badge
Creates a code coverage badge like the following:
Currently just reads from Istanbul's JSON summary reporter and downloads a badge from https://shields.io/. Don't expect too much! Send a PR if you need configuration etc.
(For Create React Apps)
package.json
):"jest": {
"coverageReporters": [
"json-summary"
]
}
npm test -- --coverage
make-coverage-badge
Resulting badge will be in ./coverage/badge.svg
.
--output-path <path>
Writes the coverage badge to the given path (relative to project root). Defaults to ./coverage/badge.svg
.
--report-path <path>
Path to a coverage report file. Defaults to ./coverage/coverage-summary.json
.
© 2019 Tom Vincent git@tlvince.com (https://tlvince.com)
Released under the MIT license.
FAQs
Create a coverage badge
The npm package make-coverage-badge receives a total of 10,640 weekly downloads. As such, make-coverage-badge popularity was classified as popular.
We found that make-coverage-badge 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.