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.
@jamsite/jamsite-cli
Advanced tools
Jamsite cli - JAMstack framework command line interface.
jamsite-cli is inteded to be installed globally, but can will work locally as well.
npm i -g @jamsite/jamsite-cli
Execute jamsite
or npx jamsite
inside your jamsite root directory (the one with package.json).
Usage: jamsite <command> [options]
Commands:
jamsite start Start jamsite server in production mode.
jamsite start-dev Start jamsite in development mode.
jamsite new Generate new site from template.
jamsite data Start node repl with jamsite data context.
jamsite build Generate static files.
jamsite build:<command> Run local build command given by name.
Options:
-h, --help Show help
FAQs
Jamsite cli - JAMstack framework cli interface
The npm package @jamsite/jamsite-cli receives a total of 1 weekly downloads. As such, @jamsite/jamsite-cli popularity was classified as not popular.
We found that @jamsite/jamsite-cli 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.