registry / @doikayt/typescript-build-config / 0.1.47
@doikayt/typescript-build-config@0.1.47
⚠ Under reviewShared build configuration for TypeScript projects — ESLint, Prettier, tsconfig, and Playwright presets
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected install hook performs package-related project setup, and no concrete attack behavior was established. The bundled PDF remains unresolved because trusted offline analysis could not determine its structure or behavior, so manual review is warranted.
Static reason
One or more suspicious static signals were detected.; source matched previously finalized malicious package; routed for review; previous stored version diff introduced dangerous source
Trigger
The postinstall hook runs automatically during installation; the PDF is not among the assets it copies.
Impact
No concrete attack impact was confirmed; the unresolved artifact prevents a clean determination.
Mechanism
The hook copies named configuration and pipeline files into the consumer project. No inspected source loads the PDF, but its behavior remains undetermined.
AI rationale
The inspected install hook performs package-related project setup, and no concrete attack behavior was established. The bundled PDF remains unresolved because trusted offline analysis could not determine its structure or behavior, so manual review is warranted.
Evidence
package.jsonsrc/postinstall.jsassets/image/jews-support-a-free-palestine-poster.pdf.lpm-inspection-Il8ecR/0-163ed93a16b3.txt
Decision evidence
public snapshotAI called this Manual Review at 82.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json automatically runs src/postinstall.js after installation.
- The postinstall hook copies named configuration and pipeline files into the consumer project.
- The hook’s asset copy list contains only the two logo files.
- The included PDF’s trusted offline analysis could not determine its structure or executable behavior.
Evidence against
- Inspected source showed no confirmed credential transfer, network send, or AI-agent control-surface mutation.
- No inspected source loads the PDF; the postinstall hook copies only the listed logos.
Behavioral surface
ChildProcessEnvironmentVarsFilesystemShell
HighEntropyStrings
Source & flagged code
7 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node src/postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node src/postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkg21"files": [
"src/",
"src/top-level/.gitignore",
"assets/image/"
],
"scripts": {
"prepack": "echo no build step required",
"postinstall": "node src/postinstall.js",
"update-all-forma
Low
Suspicious Lifecycle Evidence
package.json automatically runs src/postinstall.js after installation.
package.jsonView on unpkg · L21src/pipeline/auto-changeset.shView file
Findings
4 High4 Medium4 Low
HighInstall Time Lifecycle Scriptspackage.json
HighShips High Entropy Blobassets/image/jews-support-a-free-palestine-poster.pdf
HighKnown Malware Source Similaritysrc/playwright.js
HighPrevious Version Dangerous Deltasrc/postinstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumEnvironment Vars
MediumShips Build Helpersrc/pipeline/auto-changeset.sh
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @doikayt/typescript-build-config@0.1.47.
See all versions of @doikayt/typescript-build-config for other recorded verdicts.
- Review the evidence and your use of @doikayt/typescript-build-config@0.1.47 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.