Profit Margin Calculator Walmart

Security checks across static analysis, malware telemetry, and agentic risk

Overview

This looks like a local profit calculator with no credential or network access, but users should notice a Walmart-vs-Amazon/FBA mismatch and verify the global install source.

Before installing, confirm that the source repository is trustworthy and that the calculator’s formulas actually match Walmart/WFS fees rather than Amazon/FBA assumptions. No artifact evidence indicates credential use, data exfiltration, persistence, or destructive behavior.

Static analysis

No static analysis findings were reported for this release.

VirusTotal

VirusTotal findings are pending for this skill version.

View on VirusTotal

Risk analysis

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

The calculator may use or display assumptions that do not match Walmart Marketplace fees, which could affect business decisions.

Why it was flagged

The skill is presented as a Walmart/WFS margin calculator, but the included script text references Amazon/FBA calculations. This could cause users to overtrust marketplace-specific fee assumptions.

Skill content
"Amazon Profit Calculator - Core Engine" ... "Amazon Referral Fee Rates" ... "FBA Fulfillment Fee Reference"
Recommendation

Verify the fee formulas and field names before relying on results; the maintainer should align the code and documentation with Walmart/WFS terminology and rates.

What this means

A global install can add code or commands to the user environment, so the source should be trusted.

Why it was flagged

The documentation suggests a global npx install from an external repository-style source, and the registry entry has no separate install spec or pinned release information.

Skill content
npx skills add nexscope-ai/eCommerce-Skills --skill profit-margin-calculator-walmart -g
Recommendation

Install only after verifying the repository and version; prefer pinned releases or reviewed package sources when available.