@buntok/core@2.0.1
Core HTTP framework for Bun — Express-like, bring your own structure
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection found ordinary framework functionality and user-invoked CLI generation, without an install-time or stealthy malicious chain. The flagged dynamic code and networking are constrained to router optimization and configured application features.
Decision evidence
public snapshot- package.json has no npm lifecycle hook; it declares library exports and a CLI bin.
- Dynamic Function construction compiles registered middleware/router handlers, not downloaded code.
- CLI writes project scaffolding only after explicit create or make:docs commands.
- Network calls are configured mail-provider sends using caller-supplied message and API configuration.
- No credential harvesting, shell execution, remote payload loading, persistence, or AI-agent configuration writes found.
- No install-time execution path is declared.
- The CLI’s dynamic import is limited to the user’s local src/index.ts during explicit documentation generation.
Source & flagged code
5 flagged · loading sourcePackage source references dynamic require/import behavior.
dist/core-exports.cjsView on unpkg · L191Package source references a known benign dynamic code generation pattern.
dist/core-exports.cjsView on unpkg · L1773Source file is highly similar to a previously finalized malicious package; route for source-aware review.
Findings
Affected versions and remediation
This report applies to @buntok/core@2.0.1.
See all versions of @buntok/core for other recorded verdicts.
- Review the evidence and your use of @buntok/core@2.0.1 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.