@knapsack/app@4.107.0
Build Design Systems with Knapsack
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected runtime behavior is consistent with the package’s CLI, API client, and logging functions. The scanner’s dynamic loading and network hints did not establish a concrete attack.
Decision evidence
public snapshot- The package manifest lists build, clean, lint, and test scripts and no install lifecycle hook.
- The inspected dependency entrypoints are Babel compiler/configuration code and Knapsack core URL, role, and file-type utilities; their manifests show no install scripts.
- The CLI telemetry is identified as app-client telemetry and can be disabled with KS_DISABLE_TELEMETRY.
- The API client uses GET requests through the configured Knapsack API endpoint.
Source & flagged code
5 flaggedPackage source references dynamic require/import behavior.
dist/types/knapsack-config.jsView on unpkg · L3The package manifest lists build, clean, lint, and test scripts and no install lifecycle hook.
package.jsonView on unpkg · L110Findings
Affected versions and remediation
This report applies to @knapsack/app@4.107.0.
See all versions of @knapsack/app for other recorded verdicts.
- Review the evidence and your use of @knapsack/app@4.107.0 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.