Maximo API Explorer — IBM Maximo REST API Browser, Tester & Scaffold Generator
The AI review rates the findings as likely false positive, but the risk score (43/100) still counts them. The review covers version 0.3.0, not the analysed version 0.19.0.
Analysis record
- Analysed
- 3 months ago 14 August 2026
- Version
- v0.19.0
- Artifact
- SHA256 7338e859…808457
- Detail
- Full list
Evidence ledger
Ranked by severity · findings with a source location link to the code viewer
Publisher Evidence
Limited evidenceMarkus van Kempen
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
13 evidence rows available.
Finding Categories
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
The Maximo API Explorer extension's filesystem and network access is fully justified by its stated purpose of IBM Maximo REST API exploration. The network findings show fetch calls in extension/out/templates/carbonAssets.js:555, extension/out/templates/carbonWorkOrders.js:505, extension/out/snippets/snippetGenerator.js:154, and extension/out/export/projectExporter.js:535 — all legitimate for an API explorer that must make HTTP requests to test endpoints and generate code snippets. No credential-access findings target actual secrets; the findings summary shows 0 secret findings, meaning no .env, .ssh, or cloud credential access was detected. The 105 IoC findings are entirely XIOC extractor garbage: r.target, r.name, and schema.name are property access chains misread as domains; schemas.microsoft.com and img.shields.io are legitimate infrastructure domains; http://www.apache.org/licenses/LICENSE-2.0 is a license URL; treeprovider.js.map is a source map file path, not a domain. The 64 code-smell findings are low-severity patterns expected in any non-trivial JavaScript extension. There are 0 malware signatures, 0 malware findings, 0 obfuscation findings, and 0 tool-poisoning findings. The strongest counterargument is the low user count (22 users), which could indicate a new or niche extension with less community scrutiny. However, this does not change the conclusion because the actual findings show no malicious behavior — only documented false positive patterns. The extension performs expected IDE extension behavior: reading files for API templates, making network calls to test APIs, and writing generated snippets. This is a legitimate development tool for IBM Maximo developers, and all CVEQ findings are noise from the XIOC extractor and code-smell rules.
Key Reasons
- All IoC findings are XIOC false positives (property chains, legitimate domains, license URLs)
- Zero malware signatures and zero malware findings
- Zero secret/credential access findings
- Network activity matches stated API explorer purpose
- No obfuscation or tool-poisoning indicators
False Positive Considerations
- XIOC property access chain misinterpretation (r.target, r.name, schema.name)
- Legitimate infrastructure domains (schemas.microsoft.com, img.shields.io)
- Code-smell findings on standard JavaScript patterns
- License URL extraction (apache.org/licenses)
Reviewed 2026-04-28 · version 0.3.0; recommended action: suppress false positive; model confidence 87%.
VS Code version history
Risk trend by version
2 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates: First seen by Risky Plugins.
Pick any point on the chart, then open the Source tab to read that version's code.
Source Code Not Available
Source code is not available for this version of the extension.
About This Extension
Frequently Asked Questions
Similar Extensions
Related extensions from the same publisher or marketplace
WxO ToolBox(v2)
Markus van Kempen
WxO ToolBox
Markus van Kempen
WxO Builder
Markus van Kempen
IBM Maximo MCP for AI (Multi-IDE Connector & Tools)
Markus van Kempen
SudoSharp Language Support
Sudo
Java Script Lite
Phoebus Tecnologia