OpenVSX Registry Verified

AWS Startup Advisor

1eb44f12-36c0-5865-9e99-0091c3d8e013 | v1.0.14
51/ 100
MEDIUM risk
No change since v1.0.13
Analyst verdict
Review before use

The AI review rates the findings as likely false positive, but the risk score (51/100) still counts them.

Analysis record

Analysed
1 weeks ago
Version
v1.0.14
Artifact
SHA256 85C…B7C
Source
Findings (non-IoC)

No Findings

All security checks passed

Publisher Evidence

Low

amazonwebservices

Publisher identity, store signals, distribution reach, and warning signals used for context. Treat this as supporting evidence, not a clean bill of health.

50
Noisy-finding weight
x1.00
Publisher domain
No domain
Missing
Store verification signal
Verified publisher
Verified
Extension portfolio
1
Portfolio

13 evidence rows available.

No Threats Detected

This extension passed all security checks

AI Security Report

AI Security Review

Evidence context: threat category none; evidence quality strong.

What the extension is

aws-startup-advisor is published by amazonwebservices, the account AWS itself uses for its IDE tooling, on OpenVSX. Version 1.0.14, 15,760 users. It shows AWS notifications and curated guidance prompts in the editor. It declares no permissions and no host permissions, which fits a product whose job is to render content rather than manipulate the workspace.

Filesystem and process access

Nothing in this release shows the extension reading workspace files, writing to them, or spawning a shell. No postinstall rule fired, and there are no network-callback or manifest findings. The 39 low-severity code-smell matches and the 34 dependency matches are the normal output of scanning bundled dist/ JavaScript that carries a large npm tree. None of them describe an action this extension takes.

Credential access

Secret-access findings are zero. The credential-shaped rules that fire on almost any Node.js code touching process.env produced no hits here. AWS tooling does legitimately read ~/.aws/config and credential files, and the scan shows no sign of that happening. The only credential-adjacent artifact is XIOC-URL-http://certificates.godaddy.com/repository/0, which is the repository path of a GoDaddy root certificate baked into a bundled certificate store.

Network endpoints

Every endpoint that resolves to something real belongs to AWS: amazon.com, amazonaws.com, amazonaws.com.cn, awsapps.com, awslabs.aws, alpha.eksctl.io and signin.amazonaws-us-gov.com. That list is the extension's own product surface. The remainder are extraction artifacts. XIOC-DOMAIN-cxi.aws, XIOC-DOMAIN-xzm.aws and XIOC-DOMAIN-niu.aws are fragments of longer AWS service hostnames the extractor split mid-label, and XIOC-DOMAIN-s3.dualstack.us is a truncated S3 dualstack endpoint. XIOC-DOMAIN-emdash.case and backslash.case are misread substrings rather than anything resolvable.

The bundled-library strings account for the rest. XIOC-URL-http://schemas.openxmlformats.org/package/2006/content-types is an OOXML schema reference carried inside a library that handles Office documents. XIOC-URL-https://react-native.canny.io/feature-requests/p/fetch-streaming-body is an issue-board link shipped in a dependency's docs. The entries 1-transform.md, 2-deploy.md and 3-test.md in the endpoint list are markdown filenames, not hosts.

Strongest counterargument

287 URL and domain indicators is a large number, and read at face value it looks alarming. The counter is that the number collapses on inspection into AWS hostnames, CA repository paths, embedded library strings and split fragments. An indicator count in dist/ scales with the dependency tree, not with the intent of the extension. A genuinely malicious AWS-themed extension would show credential reads, a postinstall hook or a non-AWS exfiltration destination. This release shows none of those, and the publisher is the vendor whose services it talks to.

Key Reasons

  • Publisher is amazonwebservices, the official AWS account, and the extension is an OpenVSX mirror of a widely installed VS Code extension (15,760 users).
  • Zero malware, obfuscation, secret-access, tool-poisoning or manifest findings, and zero critical or high severity items.
  • All resolvable endpoints belong to AWS (amazonaws.com, awsapps.com, alpha.eksctl.io, signin.amazonaws-us-gov.com), matching the stated product purpose.
  • Suspicious-looking indicators such as XIOC-DOMAIN-cxi.aws, xzm.aws and niu.aws are fragments of longer AWS hostnames split by the extractor.
  • Remaining URLs trace to bundled dependencies: schemas.openxmlformats.org (OOXML schema), certificates.godaddy.com (CA repository) and react-native.canny.io (issue link).

False Positive Considerations

  • IoC extractor splitting AWS service hostnames into fragments (cxi.aws, xzm.aws, niu.aws, s3.dualstack.us)
  • Bundled dependency strings swept up as indicators (schemas.openxmlformats.org, certificates.godaddy.com, react-native.canny.io)
  • Markdown filenames (1-transform.md, 2-deploy.md, 3-test.md) parsed as network endpoints
  • Low-severity code-smell and dependency counts inflated by bundled dist/ JavaScript

Reviewed 2026-10-13; recommended action: suppress false positive; model confidence 87%.

Open VSX version history

Risk trend by version

4 analyzed versions. Each point is the latest successful scan for that version; failed zero-score scans are hidden. Dates are based on first seen by risky plugins.

Selected
51
Change since first
No change
Change from previous
No change
Versions:
First analyzed version
1.0.11
Aug 29, 2026
Risk range
51 to 51
Across analyzed versions
Latest analyzed version
1.0.14
Oct 10, 2026
Selected version
medium
Version
v1.0.14
1 weeks ago
Risk score
51
Findings
360
Change vs previous
0

Pick any point on the chart to explore that version's code below.

About This Extension

Personalized AWS notifications and curated AI prompts for startup builders — security, cost, scalability, and architecture guidance, in your IDE.

Frequently Asked Questions