@ever-gauzy/plugin-integration-plane-api@0.1.9
Ever Gauzy Plane Integration - A Proxy connecting Plane frontend to Ever Gauzy APIs
AI Security Review
scanned 20d ago · by lpm-firewall-aiThe manifest has no install lifecycle hook, and the inspected flagged files show ordinary proxy, API, DTO, and serialization behavior. Static references to network APIs and environment variables do not establish a concrete attack surface.
Static reason
No blocking static signals were detected.
Trigger
The proxy functions when an integrator imports or mounts the package and makes application requests.
Impact
No concrete malicious effect or unrelated credential transfer was established.
Mechanism
Controllers delegate to API-backed services, while DTOs, serializers, and configuration utilities support those requests.
AI rationale
The manifest has no install lifecycle hook, and the inspected flagged files show ordinary proxy, API, DTO, and serialization behavior. Static references to network APIs and environment variables do not establish a concrete attack surface.
Decision evidence
public snapshotAI called this Clean at 87.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json lists build, run, lint, and test scripts; it has no install lifecycle hook.
- The published entrypoint re-exports the proxy module, bootstrap function, configuration registry, and session-token helpers.
- The required flagged paths contain application controllers and API-backed services, DTO exports, serializers, configuration utilities, or timezone data; they do not establish a concrete attack.
- The credential helper reads API keys and tokens from the package configuration registry; inspected source did not establish an unrelated credential recipient.
Evidence against
Behavioral surface
EnvironmentVarsNetwork
HighEntropyStrings
CopyleftLicense
Source & flagged code
7 flaggedpackage.jsonView file
26"scripts": {
"build": "nest build",
"format": "prettier --write \"src/**/*.ts\" \"test/**/*.ts\"",
"start": "nest start",
"start:dev": "nodemon",
"start:debug": "nest start --debug --watch",
"start:prod": "node dist/main",
"lint": "eslint \"{src,apps,libs,test}/**/*.ts\" --fix",
"test": "jest",
"test:watch": "jest --watch",
"test:cov": "jest --coverage",
"test:debug": "node --inspect-brk -r tsconfig-paths/register -r ts-node/register node_modules/.bin/jest --runInBand",
"test:e2e": "jest --config ./test/jest-e2e.json"
},
"dependencies": {
Low
Suspicious Lifecycle Evidence
package.json lists build, run, lint, and test scripts; it has no install lifecycle hook.
package.jsonView on unpkg · L26dist/index.jsView file
4var main_1 = require("./main");
Object.defineProperty(exports, "bootstrap", { enumerable: true, get: function () { return main_1.bootstrap; } });
var plane_proxy_module_1 = require("./plane-proxy.modu
Low
Ai Review Evidence
The published entrypoint re-exports the proxy module, bootstrap function, configuration registry, and session-token helpers.
dist/index.jsView on unpkg · L4Findings
2 Medium10 Low
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowHigh Entropy Strings
LowCopyleft License
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/modules/pages/pages.controller.js
LowAi Review Evidencedist/modules/file-assets/file-assets.controller.js
LowAi Review Evidencedist/modules/file-assets/file-assets.service.js
LowAi Review Evidencedist/modules/stickies/stickies.service.js
LowAi Review Evidencedist/modules/stickies/stickies.controller.js
Affected versions and remediation
This report applies to @ever-gauzy/plugin-integration-plane-api@0.1.9.
See all versions of @ever-gauzy/plugin-integration-plane-api for other recorded verdicts.
- Review the evidence and your use of @ever-gauzy/plugin-integration-plane-api@0.1.9 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.