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.
create-solid
Advanced tools
The easiest way to get started with Solid is by using create-solid
. This CLI tool enables you to quickly start building a new Solid application, with everything set up for you. You can create a new app using the default Solid template, or by using one of the official Solid examples. To get started, use the following command:
#or
npm init solid@latest ./my-solid-app
# or
yarn create solid ./my-solid-app
create-solid
allows you to create a new Solid app within seconds. It is officially maintained by the creators of Solid, and includes a number of benefits:
npm init solid@latest
(with no arguments) launches an interactive experience that guides you through setting up a project.npm init solid@latest --example with-mdx
).FAQs
Create Solid apps with low configuration
The npm package create-solid receives a total of 994 weekly downloads. As such, create-solid popularity was classified as not popular.
We found that create-solid 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.