Add website for Chisel Operator

[lleyton]

No description provided.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Pages

Latest commit:	1cd47e6
Status:	✅  Deploy successful!
Preview URL:	https://f84fc296.chisel-operator.pages.dev
Branch Preview URL:	https://site.chisel-operator.pages.dev

View logs

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@astrojs/[email protected]	Transitive: environment, filesystem, network, shell	+61	47.1 MB	fredkschott
npm/@astrojs/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+492	107 MB	fredkschott, matthewp, natemoo-re
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+402	93.6 MB	fredkschott
npm/[email protected]	environment, filesystem, shell Transitive: network	+50	2.05 MB	lovell
npm/[email protected]	None	0	32 MB	typescript-bot

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Native code	npm/[email protected]	Location: Package overview	site/package.json site/pnpm-lock.yaml
Native code	npm/[email protected]	Location: Package overview	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	site/package.json site/pnpm-lock.yaml

View full report↗︎

Next steps

What's wrong with native code?

Contains native code which could be a vector to obscure malicious code, and generally decrease the likelihood of reproducible or reliable installs.

Ensure that native code bindings are expected. Consumers may consider pure JS and functionally similar alternatives to avoid the challenges and risks associated with native code bindings.

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]

[lleyton]

@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]
@SocketSecurity ignore npm/[email protected]