Use case · Salesforce ISVs
Pass AgentExchange Security Review in fewer rounds.
Vulkro checks your package against the areas the AgentExchange (formerly AppExchange) Security Review looks at, while you build, so fewer problems ever reach the reviewer.
01The problem
Each failed round costs a fee and weeks.
The review finds problems after you submit, and every fix means another attempt. These two facts are Salesforce’s (source).
- $999 per attemptOn a paid solution, for the first submission and for every one after it.
- Four to five weeksHow long a review typically takes. Every resubmit starts the wait again.
- Found after you submitBy the time the reviewer’s findings arrive, the code has long moved on.
02How Vulkro helps
The reviewer’s areas, checked before you submit.
Vulkro for Salesforce sorts what it finds into the six areas the review looks at, and marks each one ready or a gap, with the exact problem to fix.
Security Review readiness · acme-billingGaps in 3 of 6
An example package. The readiness checklist, the report for the reviewer and the build check are all part of Salesforce Pro.
03Why it holds up
Precise, and checkable.
- 01Caught while you writeThe VS Code extension flags a missing access check on the line that causes it, long before a reviewer would.The same checks in the editor and the pipeline
- 02753 checks147 on the live org and 606 on code and metadata.vulkro-sf checks, vulkro-sf 0.28.0
- 03Honest about gapsIn the report for the reviewer, an area the scan cannot judge is marked not evaluated, never passed.Salesforce still runs the review