Publishing a tool

Publishing is how a tool stops being just yours and becomes something other people can discover, add to their boards, and run. It's also the moment a specific version of your tool gets frozen — once published, that version becomes immutable, and any further edits move into a fresh draft.

The three states of a version

Every version of a tool is in one of three states. Knowing which one you're in tells you what you can and can't do.

A new tool always starts as a draft. Publishing moves the version to under review. Approval moves it to published.

Before you publish make sure

1. the current version has changes comparing to previous version. If your draft is identical to the previously published version, there's nothing to release.
2. you don't violate the [rules](here must be a link to rules) for public tool. Tool will be rejected if it doesn't follow any of those rules
3. you understand that version will be publicly available. It means any user will be able to see and use this version/tool, even anonymouse users with some limits.

First-time publishing

The very first time you publish anything, your profile becomes public. Other users will see your username, the list of tools you've published and some more tools stats. We won't show your sensitive info like name, email and your private drafts are never exposed.

Review

A version that's under review is queued for approval. Review consist of multiple automatic and manual steps:

1. automatic code verification for vulnerabilities RFC
2. main files format verification (artifuncs.json, main.py, index.js etc.)
3. AI agent verification - agentic LLM makes a quick-look review for vulnarabilities and issues
4. AST tree security planning
5. files size check (not bigger than 1MB)
6. files amount (not greater than 100)
7. allowed extensions verification and MIME type analysis
8. Entropy analysis (detect encrypted/packed files)
9. YARA rules
10. Review by moderators

While a tool has at least one version under review, moderators can see that tool (its metadata, source, and the version under review) so they can run the manual review step. Tools that have never been submitted for review remain private to you.

Once published

Once approved:

• The tool shows up in search results for other users.
• Other users can add the tool to their boards and run it in their own sandboxes.
• The version becomes a permanent, numbered release that sits alongside any previous releases.

From that point on, the published version is canonical. To make further changes, edit the draft that was created for you and publish again — each successful publish becomes a new immutable version sitting next to the previous ones.

What if reviewers find a problem?

Unfortunately, there isn't a proper way to handle this yet. Right now a version that's under review can't be sent back to draft or edited in place. A real review-and-revise flow is on our roadmap and we'll add it in a future release.

For now, fixes always ship as the next version. When you click Publish, a fresh draft is automatically created for you with the next version number, so you can start fixing immediately:

1. Reproduce and fix the issue in the new draft.
2. Publish the draft.
3. The new version goes through review on its own.

Once the new version is approved, it becomes the canonical release and supersedes the earlier attempt.

Common errors

• "Draft has no changes compared to the previous version." Make at least one change in the draft before trying to publish.
• "This version can no longer be published." You're looking at a version that's already under review or published. Switch to the latest draft.
• "You are not the author of this tool." Only the original author can publish a tool.

Anonymous usage

Some published tools are picked by the artifuncs team to appear on public pages at artifuncs.com/f/{handle}, where they can be tried by anonymous visitors before signing up. This is decided by admins — authors can't opt their tools in or out individually.

• Anonymous visitors share a small pool of rate-limited execution environments. They never see your draft code; only the exact version admins pin to the public page is served.
• Your handle becomes part of a permanent URL, so handles lock at the moment of first publish. Pick carefully.
• You can fill in SEO description and share image on the Sharing tab of your tool's edit page. These appear in search results and link previews once the tool goes public.
• Anonymous use is governed by the Creator Terms. Publishing implies consent to be considered for the public page.