Utah Salt Lab

Created By
Utah-SaLT-Lab10 months ago
Overview

what is Utah Salt Lab?

Utah Salt Lab is a project focused on unit testing code generated by the SecCodePLT framework, aimed at enhancing security in code generation.

how to use Utah Salt Lab?

To use Utah Salt Lab, set up a containerized environment using Docker, install the required packages, generate code from the SecCodePLT dataset, preprocess the code, and run unit tests to evaluate the generated solutions.

key features of Utah Salt Lab?

  • Containerized testing environment for security-related code.
  • Support for unit testing of 1,201 tasks from the SecCodePLT dataset.
  • Comprehensive preprocessing and result evaluation scripts.

use cases of Utah Salt Lab?

  1. Validating the security of generated code in software development.
  2. Automating unit tests for large datasets of code samples.
  3. Enhancing the reliability of AI-generated code solutions.

FAQ from Utah Salt Lab?

  • What is the purpose of the unit tests?

The unit tests are designed to ensure the security and functionality of code generated by the SecCodePLT framework.

  • How do I set up the testing environment?

You can set up the environment using the provided Dockerfile and follow the installation instructions in the README.

  • Can I use this project for any code generation tasks?

This project specifically supports unit testing for tasks generated from the SecCodePLT dataset.

Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
Utah-SaLT-Lab
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago