updated 2026-10-11 00:07 UTC

Naksha Studio

Repository

A virtual design team for Claude Code, Cursor, Windsurf, Gemini CLI, and Copilot — 26 roles, 62 commands, 15,000+ lines of expert design knowledge. Your agency's design brain, inside your terminal.

Agent Skills HTML Listed MIT

Is Naksha Studio safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.6 / 10
Provenance None
Signed commits 4%
Last push 103d ago
Compare Naksha Studio

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Naksha Studio scores 37.9/100 (Grade D), ranked #339 of 371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.6/10; 4% of recent commits are signed; last pushed 2026-06-30. Every point is earned from checkable signals — never paid placement. How scoring works →

How Naksha Studio could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Naksha Studio and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/Adityaraj0421/naksha-studio, MIT, last pushed 2026-06-30. 4% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.6/10 (scanned Oct 9, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions8
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 8
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 8
    Vulnerabilities 0

  3. Published packages None

    No registry package. Naksha Studio is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

  • 2026-09-03 OSSF Scorecard: 4.3/10

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Naksha Studio’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.

How Naksha Studio compares in Agent Skills

  1. #337 The Startup 38.9 +1.0
  2. #338 Functional Skill Creator 38.4 +0.5
  3. #339 Naksha Studio 37.9 this agent
  4. #340 Devglobe Extension 37.6 −0.3
  5. #341 Super Simple Software Factory 37.2 −0.7

Bars show each HVTrust score; the tick marks Naksha Studio’s 37.9.

Where the 37.9 comes from

HVTrust dimensions vs the Agent Skills average

37.9 / 100 · 100.0% confidence

Naksha Studio Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.7 / 25
3.1 below avg 7.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
11.6 / 17
in line with avg 12.1
Maintenance60% last-push freshness · 40% commit activity
5.1 / 20
9.0 below avg 14.1
AdoptionLog-scaled stars · package downloads
6.0 / 20
3.0 below avg 9.0

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-01
Rank Moved
Rank dropped 10 spots (#321 → #331)
2026-09-28
Activity Went Stale
No commits for 90 days
2026-09-25
Rank Moved
Rank dropped 26 spots (#294 → #320)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.6/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 103 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Naksha Studio View Agent Skills Report missing data
32.6
Activity sub-score · out of 100
#339
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-11 00:07 UTC · Repo last pushed 103 days ago

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
322
Forks
27
Last Push
2026-06-30
103 days ago
Commits (4 wk)
0
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
0
Rank Change
▼1
was #338

Analysis

Activity Inputs

32.6 / 100
StarsRepository reach
15.1 / 30
FreshnessLast push recency
10.7 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
6.7 / 20

Common questions about Naksha Studio

Public trust evidence for Naksha Studio is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Naksha Studio publish package provenance?
No published build provenance is currently detected for Naksha Studio. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Naksha Studio have an OpenSSF Scorecard?
Naksha Studio has an OpenSSF Scorecard score of 3.6/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Naksha Studio actively maintained?
Slowing down. Last push was 103 days ago — keep an eye on whether activity resumes.
What license does Naksha Studio use?
Naksha Studio ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Naksha Studio's commits signed?
4% of the last 100 commits to Naksha Studio are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Naksha Studio's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-28
Activity Went Stale
No commits for 90 days
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic

Maintain Naksha Studio?

For maintainers

HVTrust scores Naksha Studio from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 5Listed 2HVTrust 2Scorecard 1Delisted 1Surface 1Surface 1Stale 1
2026-10-01
Rank Moved
Rank dropped 10 spots (#321 → #331)
2026-09-28
Activity Went Stale
No commits for 90 days
2026-09-25
Rank Moved
Rank dropped 26 spots (#294 → #320)
2026-09-23
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Rank Moved
Rank dropped 56 spots (#238 → #294)
2026-09-23
HVTrust Changed
HVTrust up 8.3pts (32.4 → 40.7)
2026-09-22
Newly Listed
First tracked at rank #238
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-05
Rank Moved
Rank dropped 10 spots (#228 → #238)
2026-09-03
Scorecard Added
OSSF Scorecard: 4.3/10
2026-09-03
Rank Moved
Rank rose 98 spots (#319 → #221)
2026-09-03
HVTrust Changed
HVTrust up 25.7pts (16.3 → 42.0)
2026-08-26
Newly Listed
First tracked at rank #294
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 37.9 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/naksha-studio.svg)](https://hvtracker.net/agents/naksha-studio)
HTML:
<a href="https://hvtracker.net/agents/naksha-studio"><img src="https://hvtracker.net/badge/naksha-studio.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON