PHP Profiler
Based on the RiskyPlugins AI security review of the observed evidence. The review covers version 1.76.19462, not the analysed version 1.76.19559.
Analysis record
- Analysed
- Today 21 November 2026
- Version
- v1.76.19559
- Artifact
- SHA256 9fa392df…c12422
- Detail
- Full list
No findings
The analyzer reported nothing for this version.
Publisher Evidence
LowDEVSENSE
Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.
12 evidence rows available.
No findings
The analyzer reported nothing for this version.
AI Security Report
AI Security Review
Evidence context: threat category none; evidence quality moderate.
PHP Profiler is published by DEVSENSE, the group behind PHP Tools, and version 1.76.19462 carries 6,640,387 installs on the VS Code Marketplace. Its stated job is narrow: read Xdebug profiling output and let you inspect the results.
Filesystem and process access. The scan recorded nothing in the permissions list and nothing in the host permissions list, so there is no capability claim to weigh against the stated purpose. Opening a cachegrind or callgrind dump from the workspace is the whole function of a profile viewer, and a tool that renders a call tree has to read the file the user points it at. Nothing recorded shows a read outside that scope, and nothing shows a spawned process. The patterns that would make a profiler worth flagging are a shell invocation used to start Xdebug, a helper binary pulled down at install time, or a write path outside the workspace. None of those are present.
Credentials. There is no credential finding to examine. No secret-scanning hit names .env, .ssh, .git/config or a cloud credential file, and nothing was flagged for reaching into VS Code's secret storage or a credential provider. A viewer that draws timings has no use for a token or a key, and the results make no claim that it goes looking for one.
Network. The endpoint list is empty. A local dump renderer has no reason to contact a server, and the scan surfaced no URL, no telemetry host and no CDN reference to argue about. That fits a viewer that works only on files already on disk.
Strongest counterargument. The case against this reading is that a clean result proves only that the scanner had nothing to report, and the empty permission list reflects what the manifest declares rather than everything the installed code can reach. A VS Code extension inherits the editor's privileges whether or not it lists them, so absence of a permission string is weak evidence about runtime behaviour. That objection would matter more if the package were an unknown re-upload. It is a versioned release from a publisher with a long marketplace history and millions of installs. The absence is also uniform: no webview bundle, no minified JavaScript, no obfuscation hit, no malware family match. A coverage gap in one extractor leaves scattered hits behind. A result that is empty everywhere, including the signature and obfuscation checks, reads as a clean package rather than a blind spot.
What this means. The extension reads profile files the user selects and renders them. Nothing in the recorded results shows it collecting source code, contacting a remote host, or running a command that its description does not call for.
Key Reasons
- Zero findings across every tracked category, including malware signature, obfuscation and IoC extraction, for version 1.76.19462
- No declared permissions and no host permissions, so there is no capability claim exceeding the stated Xdebug profile viewing purpose
- No network endpoints recorded, consistent with a viewer that renders local cachegrind and callgrind dumps
- No credential, secret or postinstall finding naming .env, .ssh, .git/config or VS Code secret storage
- Published by DEVSENSE with 6,640,387 installs on the VS Code Marketplace, an established publisher rather than a low-install re-upload
False Positive Considerations
- Empty result set means there are no code-smell or IoC hits to reconcile in the first place
- Profile viewers legitimately read workspace files, so any future filesystem finding would need runtime context
- Dist-bundled JavaScript in VS Code extensions routinely generates obfuscation and IoC noise that is absent here
Reviewed 2026-10-27 · version 1.76.19462; recommended action: no action; model confidence 85%.
VS Code version history
Risk trend by version
30 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