Security News
The Risks of Misguided Research in Supply Chain Security
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
EXPERIMENTAL
:warning: Barely works, zero tests, hardcoded paths
git clone this repo and cd into it
rm src/examples/hello/hellobeaker_client.ts
npm run gen src/examples/hello/hello.json src/examples/hello
npm run hello
To generate a client, use beaker-pyteal to create an Application and write the app spec to json
import json
from beaker import Application
from beaker.client import ApplicationClient
class App(Application):
#...
#...
app_client = ApplicationClient(algod_client, App(), signer=signer)
with open("app.json", "w") as f:
f.write(json.dumps(app_client.application_spec()))
npm run gen $PATH_TO_APP_SPEC_JSON $PATH_TO_WHERE_CLIENT_SHOULD_BE_WRITTEN
Please report issues (bound to be lots)
FAQs
> :warning: **Experimental. Zero tests. Please report issues**
The npm package beaker-ts receives a total of 176 weekly downloads. As such, beaker-ts popularity was classified as not popular.
We found that beaker-ts 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
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.