registry / @knapsack/app / 4.106.2
@knapsack/app@4.106.2
⚠ Under reviewBuild Design Systems with Knapsack
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe package has no install lifecycle hook, and inspected API requests target its configured service API. Source for selected imported dependencies is unavailable, so the dependency review rules prevent a clean verdict.
Static reason
No blocking static signals were detected.
Trigger
Importing the package or using its runtime APIs may load those dependencies.
Impact
The unavailable dependency source prevents a clean determination; no concrete attack behavior was established.
Mechanism
The manifest declares same-version Knapsack dependencies that the package entrypoint and runtime modules import; their behavior could not be verified from available source.
AI rationale
The package has no install lifecycle hook, and inspected API requests target its configured service API. Source for selected imported dependencies is unavailable, so the dependency review rules prevent a clean verdict.
Evidence
package.jsondist/index.jsdist/lib/api-client.js
Decision evidence
public snapshotAI called this Manual Review at 78.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest declares same-version Knapsack dependencies, including @knapsack/core.
- The package entrypoint imports internal server and bootstrap modules; those paths also depend on unavailable Knapsack modules.
- The API client calls the configured Knapsack API endpoint for ordinary service requests.
Evidence against
- The manifest has no preinstall, install, or postinstall hook.
- The inspected API client sends requests to the configured service API endpoint.
Behavioral surface
ChildProcessDynamicRequireEnvironmentVarsFilesystemNetworkShellWebSocket
HighEntropyStringsUrlStrings
CopyleftLicense
Source & flagged code
5 flaggeddist/types/knapsack-config.jsView file
3exports.KnapsackConfigSchema = void 0;
L4: const zod_1 = require("zod");
L5: const file_utils_1 = require("@knapsack/file-utils");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/types/knapsack-config.jsView on unpkg · L3package.jsonView file
40"@knapsack/core": "4.106.2",
"@knapsack/creator-utils": "4.106.2",
"@knapsack/design-token-utils": "4.106.2",
"@knapsack/file-utils": "4.106.2",
"@knapsack/ks-file-
Low
Suspicious Dependency Evidence
The manifest declares same-version Knapsack dependencies, including @knapsack/core.
package.jsonView on unpkg · L4036"dependencies": {
"@babel/core": "^7.29.6",
"@clack/prompts": "^0.11.0",
"@knapsack/babel-config-starter": "4.106.2",
"@knapsack/core": "4.106.2",
"@knapsack/cr
Findings
3 Medium9 Low
MediumDynamic Requiredist/types/knapsack-config.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowCopyleft License
LowSuspicious Dependency Evidencepackage.json
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/lib/api-client.js
LowSuspicious Dependency Evidencepackage.json
Affected versions and remediation
This report applies to @knapsack/app@4.106.2.
See all versions of @knapsack/app for other recorded verdicts.
- Review the evidence and your use of @knapsack/app@4.106.2 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.