registry / @knapsack/app / 4.106.3
@knapsack/app@4.106.3
⚠ Under reviewBuild Design Systems with Knapsack
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected source shows no install hook or confirmed attack behavior. Several same-vendor dependencies are directly imported by published entrypoints, and their implementations were unavailable for inspection, so the verdict remains unresolved.
Static reason
No blocking static signals were detected.
Trigger
Using the published CLI or importing the library.
Impact
The available source does not establish malicious behavior, but the unresolved dependency implementations prevent a clean verdict.
Mechanism
The entrypoints load local runtime code that imports same-vendor packages whose behavior could not be verified in this snapshot.
AI rationale
The inspected source shows no install hook or confirmed attack behavior. Several same-vendor dependencies are directly imported by published entrypoints, and their implementations were unavailable for inspection, so the verdict remains unresolved.
Evidence
package.jsondist/cli/knapsack-cli.jsdist/lib/api-client.jsdist/lib/ks-urls.jscli.js
Decision evidence
public snapshotAI called this Manual Review at 77.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest exposes a CLI and library entrypoint and lists no install lifecycle hook.
- The CLI and library import same-vendor runtime dependencies, including packages declared at version 4.106.3.
- The available API client delegates URL construction and requests to imported Knapsack packages; their implementation is not available in the inspected source.
Evidence against
- The manifest’s scripts are build, clean, lint, and test; none is an install hook.
- The CLI wrapper loads the package’s local CLI entrypoint.
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
5"bin": {
"knapsack": "cli.js",
"knapsack-build-tokens": "build-tokens.js"
},
"types": "./dist/index.d.ts",
"exports": {
".": {
"types": "./dist/index.d.ts",
"default": "./dist/index.js"
},
"./api-info": {
Low
Suspicious Lifecycle Evidence
The manifest exposes a CLI and library entrypoint and lists no install lifecycle hook.
package.jsonView on unpkg · L539"@knapsack/babel-config-starter": "4.106.3",
"@knapsack/core": "4.106.3",
"@knapsack/creator-utils": "4.106.3",
"@knapsack/design-token-utils": "4.106.3",
"@knapsack/file-utils": "4.106.3",
"@knapsack/ks-file-utils": "4.106.3",
"@knapsack/logger": "4.106.3",
"@knapsack/renderer-client": "4.106.3",
"@knapsack/rendering-utils": "4.106.3",
"@knapsack/schema-utils": "4.106.3",
"@knapsack/types": "4.106.3",
"@knapsack/utils": "4.106.3",
"chokidar":
Findings
3 Medium9 Low
MediumDynamic Requiredist/types/knapsack-config.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowCopyleft License
LowSuspicious Lifecycle Evidencepackage.json
LowSuspicious Dependency Evidencepackage.json
LowSuspicious Dependency Evidencedist/cli/knapsack-cli.js
LowSuspicious Dependency Evidencedist/lib/api-client.js
Affected versions and remediation
This report applies to @knapsack/app@4.106.3.
See all versions of @knapsack/app for other recorded verdicts.
- Review the evidence and your use of @knapsack/app@4.106.3 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.