Is Secure Sdlc Agents safe and trustworthy?

tashan scores Secure Sdlc Agents on public evidence — tashan score 41.0/100, it is currently active, note: a single primary maintainer (bus-factor risk). Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Secure Sdlc Agents?

Configure it from its source repository — it is a remote / registry server.

Who maintains Secure Sdlc Agents?

1 GitHub contributors, source: Kaademos/secure-sdlc-agents.

‹ The Index

Secure Sdlc Agents

plugin

A team of 8 AI security specialists embedded in your coding workflow — covering every phase of the Software Development Lifecycle. Includes AppSec Engineer, GRC Analyst, Cloud/Platform Engineer, Dev Lead, Release Manager, Security Champion, Product Manager, and AI Security Engineer. Each agent is invoked at the exact phase where their expertise prevents real vulnerabilities: STRIDE threat modelling, ASVS-mapped requirements, IaC security review, SAST triage, compliance attestation, and pre-relea

Works with: Claude Code (native)
native: this artifact type is that client's own format

Category: Security — see all ranked ›

Work: Security review · Regulatory compliance

Who it is for: Security engineer · Legal / compliance

Install (Claude Code):

/plugin marketplace add anthropics/claude-plugins-community
/plugin install secure-sdlc-agents@claude-community

solid

“20 worked examples, 10 tools documented; short of deep on a stated limitation; read with 2 linked doc(s)”

This grade is wrong ›

tashan score: 41.0
Instruction depth: 78.0 (solid — documents the job properly, with examples you could follow)
Adoption: 1 repos
Upkeep: 57.0
Freshness: 83.0
Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
Health: active
GitHub stars: 12
Contributors: 1
License: MIT

Security audit

Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Secure Sdlc Agents scores 41 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.

The whole series behind any row, back to the first day we measured it
The replacement, named — not just the news that something died
tashan doctor over your own config, on your own machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/plugin-kaademos-secure-sdlc-agents-secure-sdlc-agents.svg)](https://tashan.sh/capability/plugin-kaademos-secure-sdlc-agents-secure-sdlc-agents.html)

source ↗ · plugin:kaademos/secure-sdlc-agents/secure-sdlc-agents

Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.

Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.

Measured 2026-09-13 · scorer s5 · how · something wrong here?