registry / wrong-notebook / 2026.10.23
wrong-notebook@2026.10.23
⚠ Under review错题本：上传题目图片，由 AI 识别、解析并标注知识点，支持练习、统计与打印导出
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe inspected install hook performs product setup by generating the package's Prisma Client, with no attack behavior established in that code. Because server.js loads Next.js and its dependency snapshot is unresolved, the runtime review remains incomplete.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package runs its postinstall; starting the service loads Next.js.
Impact
No confirmed attack impact; the unverified runtime dependency prevents a clean determination.
Mechanism
The package lifecycle generates its own Prisma Client. The server then requires Next.js, whose dependency source was unavailable in the inspected snapshot.
AI rationale
The inspected install hook performs product setup by generating the package's Prisma Client, with no attack behavior established in that code. Because server.js loads Next.js and its dependency snapshot is unresolved, the runtime review remains incomplete.
Evidence
package.jsonserver.js
Decision evidence
public snapshotAI called this Manual Review at 76.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json declares a postinstall that runs the package CLI's prepare-client command.
- The CLI resolves the local Prisma CLI and runs client generation against the package's Prisma schema.
- server.js directly loads Next.js, and the inspected dependency snapshot for Next.js is unresolved, leaving this runtime dependency unverified.
Evidence against
- The package lifecycle command generates its own Prisma Client; inspected launcher code also documents generation as setup when install scripts were skipped.
- The inspected Prisma dependency's postinstall runs its own client-generation script.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetwork
HighEntropyStrings
Source & flagged code
6 flaggedpackage.jsonView file
•scripts registry_only=start
Critical
Manifest Confusion
Tarball package.json differs from the npm registry version manifest for scripts or dependency sets.
package.jsonView on unpkg•scripts.postinstall = node bin/wrong-notebook.js prepare-client
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node bin/wrong-notebook.js prepare-client
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg.next/server/chunks/ssr/src_1o363ao._.jsView file
Findings
1 Critical1 High7 Medium3 Low
CriticalManifest Confusionpackage.json
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumSecret Pattern.next/server/chunks/ssr/src_1o363ao._.js
MediumDynamic Requirebin/wrong-notebook.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
MediumSecret Pattern.next/static/chunks/27fr34_1v7xyh.js
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
Affected versions and remediation
This report applies to wrong-notebook@2026.10.23.
See all versions of wrong-notebook for other recorded verdicts.
- Review the evidence and your use of wrong-notebook@2026.10.23 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.