updated 2026-10-11 00:07 UTC

Deeptide

Repository Website

Built by DeepSeek, for DeepSeek — a Swift-native macOS coding agent

Agent Skills Rust Listed MIT

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

OSSF Scorecard 3.6 / 10
Provenance None
Signed commits 53%
Last push 50d ago
Advisories None known
Compare Deeptide

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Deeptide scores 49.9/100 (Grade D), ranked #241 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.6/10; 53% of recent commits are signed; no published advisory affects its latest release (deeptide); last pushed 2026-08-22. Every point is earned from checkable signals — never paid placement. How scoring works →

How Deeptide 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 Deeptide and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.

  1. Source Partly signed

    github.com/paean-ai/deeptide, MIT, last pushed 2026-08-22. 53% 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 Sep 30, 2026). The checks that decide who can get a change released:

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

  3. Published packages Linked, not attested

    • npm deeptide Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: deeptide 0.11.8. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

  • 2026-08-30 OSSF Scorecard: 4.3/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

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

Verify this score yourself

Every build re-issues Deeptide’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 Deeptide compares in Agent Skills

  1. #239 Jezweb Claude Skills 50.0 +0.1
  2. #240 Claude OSINT 49.9 ±0
  3. #241 Deeptide 49.9 this agent
  4. #242 Xint 49.7 −0.2
  5. #243 Garden Skills 49.7 −0.2

Bars show each HVTrust score; the tick marks Deeptide’s 49.9.

Where the 49.9 comes from

HVTrust dimensions vs the Agent Skills average

49.9 / 100 · 100.0% confidence

Deeptide Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.2 / 25
0.6 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
8.7 / 20
5.4 below avg 14.1
AdoptionLog-scaled stars · package downloads
9.1 / 20
in line with 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-10
Grade Changed
Trust grade C → D
2026-10-09
Grade Changed
Trust grade D → C
2026-10-01
Grade Changed
Trust grade C → D
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.
Refresh maintenance signals The repo was last pushed 50 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Deeptide View Agent Skills Report missing data
46.5
Activity sub-score · out of 100
#241
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 B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

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

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars
1.1k
Forks
139
Last Push
2026-08-22
50 days ago
Commits (4 wk)
0
Downloads (7d)
21
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▼1
was #240

Analysis

Activity Inputs

46.5 / 100
StarsRepository reach
18.3 / 30
FreshnessLast push recency
18.1 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
10.0 / 20

Common questions about Deeptide

Public trust evidence for Deeptide 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 Deeptide publish package provenance?
No published build provenance is currently detected for Deeptide. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Deeptide have an OpenSSF Scorecard?
Deeptide 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 Deeptide actively maintained?
Slowing down. Last push was 50 days ago — keep an eye on whether activity resumes.
What license does Deeptide use?
Deeptide ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Deeptide's commits signed?
53% of the last 100 commits to Deeptide 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
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
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 Deeptide'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-23
Provider Added
Runtime surface grew — new detected provider dependencies: Brave Search, DeepSeek

Maintain Deeptide?

For maintainers

HVTrust scores Deeptide 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 11Grade 5HVTrust 3Listed 2Scorecard 1Delisted 1Surface 1
2026-10-10
Grade Changed
Trust grade C → D
2026-10-09
Grade Changed
Trust grade D → C
2026-10-01
Grade Changed
Trust grade C → D
2026-09-25
Rank Moved
Rank dropped 21 spots (#214 → #235)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Brave Search, DeepSeek
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 101 spots (#314 → #213)
2026-09-23
HVTrust Changed
HVTrust up 26.4pts (24.1 → 50.5)
2026-09-22
Newly Listed
First tracked at rank #314
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-07
Rank Moved
Rank dropped 15 spots (#114 → #129)
2026-09-05
Rank Moved
Rank dropped 26 spots (#83 → #109)
2026-09-03
Grade Changed
Trust grade D → C
2026-09-03
Rank Moved
Rank rose 162 spots (#239 → #77)
2026-09-03
HVTrust Changed
HVTrust up 20.6pts (36.4 → 57.0)
2026-09-02
Rank Moved
Rank dropped 13 spots (#226 → #239)
2026-09-01
Rank Moved
Rank dropped 13 spots (#213 → #226)
2026-08-31
Rank Moved
Rank dropped 17 spots (#196 → #213)
2026-08-30
Scorecard Added
OSSF Scorecard: 4.3/10
2026-08-30
Rank Moved
Rank rose 83 spots (#279 → #196)
2026-08-30
HVTrust Changed
HVTrust up 17.2pts (19.3 → 36.5)
2026-08-29
Rank Moved
Rank dropped 11 spots (#268 → #279)
2026-08-28
Rank Moved
Rank dropped 13 spots (#255 → #268)
2026-08-26
Newly Listed
First tracked at rank #252
GitHub → Website → npm: deeptide

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Skills

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