registry / @bigbinary/neeto-editor-frontend / 2.0.10
@bigbinary/neeto-editor-frontend@2.0.10
neetoEditor is the library that drives the rich text experience in all neeto products built at BigBinary
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest exposes a rich text editor, and the inspected network calls support its upload and knowledge-base features. The lifecycle script and flagged dynamic require do not show malicious behavior.
Static reason
No blocking static signals were detected.
Trigger
Upload calls occur when the editor's upload feature is used; knowledge-base requests use the configured knowledge-base service.
Impact
These behaviors support editor uploads, knowledge-base lookup and compatibility; no malicious impact was identified.
Mechanism
The package calls application-relative direct-upload routes and sends article queries to `globalProps.kbUrl` using the organization API key. A guarded fallback attempts to load Node's crypto module when browser and global crypto are unavailable.
AI rationale
The manifest exposes a rich text editor, and the inspected network calls support its upload and knowledge-base features. The lifecycle script and flagged dynamic require do not show malicious behavior.
Network endpoints3
/api/direct_uploads//neeto_editor/api/v1/direct_uploads/attachglobalProps.kbUrl + /api/v1/articles
Decision evidence
public snapshotAI called this Clean at 95.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The package exports rich text editor components and related utilities through its import and require entry points.
- The only lifecycle script shown is `prepare: husky install`; there is no install, preinstall or postinstall hook.
- Upload requests use application-relative direct-upload routes and are defined as editor upload helpers.
- Knowledge-base article requests use the configured `globalProps.kbUrl` service and its organization API key.
- The flagged dynamic `require('crypto')` is a guarded Node.js fallback in a crypto compatibility helper.
Evidence against
- The scanner flags network and dynamic-require behavior, but the inspected code ties these to editor uploads, knowledge-base lookup and crypto compatibility.
- No unrelated collector host or automatic install-time data transfer was identified.
Behavioral surface
CryptoDynamicRequireEnvironmentVarsEvalFilesystemNetwork
Source & flagged code
4 flaggeddist/chunk-CeoqieEt.jsView file
4182try {
L4183: new Function("");
L4184: return true;
Low
Eval
Package source references a known benign dynamic code generation pattern.
dist/chunk-CeoqieEt.jsView on unpkg · L4182dist/chunk-OP-lX765.jsView file
66L67: /** @type {import("neetocommons/react-utils").ZustandStoreHook} */
L68: var useFileUploadStore = create$1(withImmutableActions(function (set, get) {
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/chunk-OP-lX765.jsView on unpkg · L66dist/v2/styles.cssView file
Findings
1 Critical1 High4 Medium6 Low
CriticalManifest Confusionpackage.json
HighSemantic Analysis Limiteddist/v2/styles.css
MediumDynamic Requiredist/chunk-OP-lX765.js
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowEvaldist/chunk-CeoqieEt.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
Affected versions and remediation
This report applies to @bigbinary/neeto-editor-frontend@2.0.10.
See all versions of @bigbinary/neeto-editor-frontend for other recorded verdicts.
- Review the evidence and your use of @bigbinary/neeto-editor-frontend@2.0.10 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.