t-tech/SynthComp
Viewer • Updated • 790 • 163 • 13
nomadicsynth PRO
nomadicsynth
AI & ML interests
architecture research, knowledge discovery
Recent Activity
liked a dataset 2 days ago
t-tech/SynthComp liked a dataset 2 days ago
scholarweave/arxiv-latex liked a model 7 days ago
Qwen/Qwen3-0.6BOrganizations
liked 2
datasets 2 days ago
liked a
model 7 days ago
liked a
model about 1 month ago
reacted to ajibawa-2023's post with 🔥 about 1 month ago
Post
6921
Shell-Code-Large
Dataset: ajibawa-2023/Shell-Code-Large
Shell-Code-Large is a large-scale corpus of Shell scripting source code comprising approximately 640,000 code samples stored in JSON Lines (.jsonl) format. The dataset is designed to support research in large language model (LLM) pretraining, code intelligence, DevOps automation, cloud infrastructure engineering, system administration, and software engineering automation.
By providing a high-volume, language-specific corpus focused exclusively on Shell scripting, Shell-Code-Large enables systematic experimentation in automation workflows, deployment pipelines, infrastructure management, and command-line tooling. These domains remain foundational to Linux systems, cloud-native platforms, CI/CD environments, and modern DevOps practices.
Shell-Code-Large addresses the need for a dedicated Shell-focused dataset at substantial scale, enabling targeted research into scripting patterns, command composition, workflow orchestration, infrastructure automation, and operational engineering practices
Dataset: ajibawa-2023/Shell-Code-Large
Shell-Code-Large is a large-scale corpus of Shell scripting source code comprising approximately 640,000 code samples stored in JSON Lines (.jsonl) format. The dataset is designed to support research in large language model (LLM) pretraining, code intelligence, DevOps automation, cloud infrastructure engineering, system administration, and software engineering automation.
By providing a high-volume, language-specific corpus focused exclusively on Shell scripting, Shell-Code-Large enables systematic experimentation in automation workflows, deployment pipelines, infrastructure management, and command-line tooling. These domains remain foundational to Linux systems, cloud-native platforms, CI/CD environments, and modern DevOps practices.
Shell-Code-Large addresses the need for a dedicated Shell-focused dataset at substantial scale, enabling targeted research into scripting patterns, command composition, workflow orchestration, infrastructure automation, and operational engineering practices
liked a
model about 2 months ago
updated a
dataset about 2 months ago
published a
dataset about 2 months ago
liked a
model 2 months ago
liked a
dataset 2 months ago
updated a
model 2 months ago
liked 2
datasets 2 months ago
updated a
dataset 3 months ago
published a
dataset 3 months ago
liked a
Space 3 months ago
reacted to telcom's post with 👍 4 months ago
Post
211
We have published a complete paper about AetnaMem
Check it out here.
Please refer to the technical paper below.
https://github.com/aetna000/aetnamem/blob/e24d5aa74e62dbebeeb28a2e49b5c4d2006bbb4d/paper/aetnamem-control-plane.pdf
Check the benchmark
Aetna000/MemoryStackBench
Check it out here.
Please refer to the technical paper below.
https://github.com/aetna000/aetnamem/blob/e24d5aa74e62dbebeeb28a2e49b5c4d2006bbb4d/paper/aetnamem-control-plane.pdf
Check the benchmark
Aetna000/MemoryStackBench
- 4 replies
upvoted an article 6 months ago
Article
Rank-Stabilized LoRA: Unlocking the Potential of LoRA Fine-Tuning
damjan-k
• • 33 reacted to scthornton's post with 👍 6 months ago
Post
2194
# SecureCode: Security-Aware Code Models
**A collection of 8 code models (3B–20B) trained to behave like a security reviewer.**
## The Problem
Code assistants frequently recommend patterns that pass tests but fail security review—string-built SQL, brittle auth logic, unsafe parsing, insecure defaults, and more. I built SecureCode to address this gap.
## What SecureCode Does
- **Identify vulnerable patterns** and explain why they're risky
- **Outline plausible abuse paths** (defensive framing)
- **Propose secure rewrites** (drop-in replacements where possible)
- **Include defense-in-depth guidance** + regression tests/checks
## Resources
| Resource | Link |
|----------|------|
| Models | https://huggingface.co/collections/scthornton/securecode |
| Dataset | scthornton/securecode (2,185 examples) |
| Paper | https://arxiv.org/abs/2512.18542 |
## How to Test It
Copy and paste this prompt with your code:
## Dataset Coverage
SecureCode covers both traditional and emerging security domains:
- **Traditional web security** (OWASP Top 10 2021)
- **AI/ML security** (OWASP LLM Top 10 2025): prompt injection, RAG poisoning, model extraction, agentic AI patterns
## We Want Your Feedback
We're looking for real-world contributions:
- **Real snippets**: Share code that "slipped through review once" (sanitized is fine)
- **False positives/negatives**: What didn't work as expected?
- **CVE-grounded examples**: New vulnerability patterns you've encountered
**Please include**: language/framework + what the correct remediation looks like in your environment.
---
**Have contributions or suggestions?** I'd be happy to hear them. Thanks for your support!
**A collection of 8 code models (3B–20B) trained to behave like a security reviewer.**
## The Problem
Code assistants frequently recommend patterns that pass tests but fail security review—string-built SQL, brittle auth logic, unsafe parsing, insecure defaults, and more. I built SecureCode to address this gap.
## What SecureCode Does
- **Identify vulnerable patterns** and explain why they're risky
- **Outline plausible abuse paths** (defensive framing)
- **Propose secure rewrites** (drop-in replacements where possible)
- **Include defense-in-depth guidance** + regression tests/checks
## Resources
| Resource | Link |
|----------|------|
| Models | https://huggingface.co/collections/scthornton/securecode |
| Dataset | scthornton/securecode (2,185 examples) |
| Paper | https://arxiv.org/abs/2512.18542 |
## How to Test It
Copy and paste this prompt with your code:
You are a senior application security engineer. Review the code below.
Output:
(1) findings with severity,
(2) likely exploit scenarios (high level),
(3) secure rewrite,
(4) defense-in-depth recommendations,
(5) regression tests/checks.
Code: `...`## Dataset Coverage
SecureCode covers both traditional and emerging security domains:
- **Traditional web security** (OWASP Top 10 2021)
- **AI/ML security** (OWASP LLM Top 10 2025): prompt injection, RAG poisoning, model extraction, agentic AI patterns
## We Want Your Feedback
We're looking for real-world contributions:
- **Real snippets**: Share code that "slipped through review once" (sanitized is fine)
- **False positives/negatives**: What didn't work as expected?
- **CVE-grounded examples**: New vulnerability patterns you've encountered
**Please include**: language/framework + what the correct remediation looks like in your environment.
---
**Have contributions or suggestions?** I'd be happy to hear them. Thanks for your support!
i foresee a new industry on Fiverr adding prompt injections to people's CVs. The future is hilarious, if you don't mind a bit of chaos.