Exports and sharing
Export findings, share a repository inbox or a run with guests, and publish a run report.
Export findings
Click the download icon beside Group by (Export findings). V12 saves the findings the view and filters show, collapsed groups included, as a zip: one Markdown file per finding with its report, locations, proof of concept and proposed fix — the text Copy as prompt gives — a .patch beside it when the fix has a patch, and a README.md listing them. Each file names the code V12 read: every repository's remote (for a GitHub repository), the branch or pull request, and the commit; a .patch starts with lines naming the commit its fix was written against. While it prepares the zip the button reads Preparing 140 of 512…, and Cancel stops it. If the view is empty, V12 says "Nothing to export". A zip holds at most 5,000 findings.
The files together can contain at most 64 MiB of UTF-8 text, including patches and the README, and the finished zip can be at most 64 MiB. If either limit is exceeded, nothing is downloaded; narrow the list and try again. Compression runs in the background, so Cancel also stops it while the zip is being prepared. Leaving the page cancels the export.
Export run findings
Use this for a complete run whose findings aren't in the inbox.
Open the run and go to its Findings section.
Click Export and choose CSV, JSON or Markdown.
The file holds the run's findings, up to 5,000. It downloads as v12-<N>.csv, v12-<N>.json or v12-<N>.md, where N is the run's number, shown as Run #N on its page. You can download up to three run exports at a time; wait for one to finish before you start a fourth.
Each finding carries the ID it has in the inbox, such as F-12, in keys (CSV and JSON) or at the start of its heading (Markdown). A finding that isn't in the inbox has no ID.
Share a repository inbox
An Admin can give someone outside the organization who has a V12 account access to one repository's findings.
Open the repository's Share inbox page at /<organization>/. Nothing in V12 links to it, so type the address.
Type the person's email in Existing V12 user email and click Share.
Guests can read, triage and comment on the repository's findings. They can't start runs, see the rest of the organization, or see links to the repository or its runs. The page lists each guest; Remove revokes their access.
Guests find the repository under Shared with you in Settings → Repositories of their personal workspace, where Open opens its findings.
Share a run with guest links
A guest link opens one run to people outside your organization, with no V12 account needed. The person who started the run and Admins can make and manage its links once the run is queued: while it runs, after it fails or is cancelled, and when it completes, whatever it found.
Open the run and click Share.
Under Guest links, click New link. Optionally type a label, then choose a role and lifetime.
Click Create and copy to copy the link, https://v12.sh/s/v12s_….
| Role | Guests can |
|---|---|
| Can view | Read the findings, their reports and discussion |
| Can comment (the default) | Also comment and reply |
| Can triage | Also change status and severity. Changes apply to the finding everywhere in your inbox. |
A link lasts 1, 7, 14 (the default) or 30 days, or never expires. Changing a live link's role or lifetime in its row takes effect at once. A new lifetime counts from today. Rename and Revoke are under ….
Revoking cuts off a link's guests at once and leaves their comments and changes in your inbox.
A run can have 20 live links and 250 guests on them; revoking a link frees its guests' places. A link keeps working after its creator leaves your organization, until it expires or is revoked.
What guests see and do
Can view guests read anonymously. Other guests first pick a display name, which they can change until they first comment or change a finding.
Guests see the run's status and progress, the same steps your team sees on the run's page. While the run is queued or running the page updates on its own, and its findings appear once the run completes and they reach your inbox.
Guests see the findings in your inbox's list, with their evidence and whole discussion, and members named by username. Statuses are the ones at the commit the run read in each repository. A fix recorded on a later commit does not change them.
Guests can export the findings they see the same way, and copy one with Copy as prompt; their files and prompts leave out the guest link's address.
Guests' comments and changes show in your inbox under their name, marked guest. V12 limits how often guests can comment and change findings.
Guests never:
- see other runs, other repositories, the run's Steers or anyone's email;
- assign a finding, or mark it a duplicate;
- copy a finding as a prompt from its page, or reference or attach files;
- change the status of a finding your organization marked Won't fix, accepted risks included.
A guest's Open, Fixed or False positive applies at the commit the run read in each repository, including other runs' reports of the finding there, and never to code outside the run.
Share a run report
Share on a run's page creates a read-only report at https://v12.sh/share/ followed by a random code. Anyone with the link can read it without a V12 account. The person who started the run and Admins can share it.
Once shared, Share opens the report, and Stop sharing turns the link off at once. Where Share opens the run's guest links dialog instead, use Publish, Open and Unpublish under Public summary. Unpublish also takes effect at once.
You can share a report only for a complete run that carried at least one Steer, where every source is a named repository pinned to a commit and none is a public repository added without the V12 GitHub App.
Public run reports lists exactly what it publishes: no code, analysis or comments. Its severities are the run's own, not your inbox's.