daydreams

Daydreams is a set of tools for building agents for commerce

Agent Frameworks TypeScript Grade D Listed MIT
35.8/100
Rank #1227 of 1328
Compare daydreams

How does it stack up against its Agent Frameworks neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-03-01 · 201d ago
Recent change
No recent signal change

Is daydreams safe? daydreams scores 35.8/100 (Grade D), ranked #1227 of 1328 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.8/10; 69% of recent commits are signed; last pushed 2026-03-01. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Frameworks

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-08
Rank Moved
Rank dropped 13 spots (#1195 → #1208)
2026-09-07
Rank Moved
Rank dropped 17 spots (#1178 → #1195)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1163 → #1178)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/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 201 days ago. Fresh activity helps separate stable projects from stale ones.
26.7
Activity sub-score · out of 100
#107

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-09-18 13:03 UTC · Repo last pushed 201 days ago — may be stale

Rank Trend

2026-08-11 2026-09-18

Activity & Reach

Stars
619
Forks
135
Last Push
2026-03-01
201 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
19
Rank Change
=
was #1227

Analysis

HVTrust Dimensions vs Agent Frameworks

35.8 / 100 · 100.0% confidence

daydreams Agent Frameworks average (122 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.2 / 25
1.5 below avg 9.7
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.8 below avg 11.6
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
0.7 below avg 12.4
Maintenance60% last-push freshness · 40% commit activity
0 / 20
13.9 below avg 13.9
AdoptionLog-scaled stars · package downloads
6.7 / 20
4.5 below avg 11.2

Activity Inputs

26.7 / 100
StarsRepository reach
16.8 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
9.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.8 / 10
OpenSSF Scorecard · scanned Sep 9, 2026
Signed Commits
69%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 8
CII-Best-Practices 0
Code-Review 0
Contributors 3
Dangerous-Workflow 10
Dependency-Update-Tool 10
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is daydreams safe?

Public trust evidence for daydreams 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 daydreams publish package provenance?
No published build provenance is currently detected for daydreams. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does daydreams have an OpenSSF Scorecard?
daydreams has an OpenSSF Scorecard score of 3.8/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 daydreams actively maintained?
Stale. The repository has not been pushed to in 201 days. Consider whether the project is still being maintained.
What license does daydreams use?
daydreams ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are daydreams's commits signed?
69% of the last 100 commits to daydreams 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
high confidence
Implemented
daydreams appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
5 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
2 tags
Broad capability areas detected.
  • code
  • search
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

Maintain daydreams?

For maintainers

HVTrust scores daydreams 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.

Reputation Timeline

Signal history
Rank 16Listed 1HVTrust 1Scorecard 1
2026-09-08
Rank Moved
Rank dropped 13 spots (#1195 → #1208)
2026-09-07
Rank Moved
Rank dropped 17 spots (#1178 → #1195)
2026-09-06
Rank Moved
Rank dropped 15 spots (#1163 → #1178)
2026-09-05
Rank Moved
Rank dropped 32 spots (#1131 → #1163)
2026-09-04
Rank Moved
Rank dropped 17 spots (#1114 → #1131)
2026-09-03
Rank Moved
Rank dropped 50 spots (#1064 → #1114)
2026-09-02
Rank Moved
Rank dropped 45 spots (#1019 → #1064)
2026-09-01
Rank Moved
Rank dropped 40 spots (#979 → #1019)
2026-08-31
Rank Moved
Rank dropped 31 spots (#948 → #979)
2026-08-30
Rank Moved
Rank dropped 43 spots (#905 → #948)
2026-08-29
Scorecard Added
OSSF Scorecard: 3.8/10
2026-08-29
Rank Moved
Rank rose 400 spots (#1305 → #905)
2026-08-29
HVTrust Changed
HVTrust up 22.7pts (13.1 → 35.8)
2026-08-26
Rank Moved
Rank dropped 11 spots (#1290 → #1301)
2026-08-16
Rank Moved
Rank dropped 25 spots (#1264 → #1289)
2026-08-10
Rank Moved
Rank dropped 80 spots (#1180 → #1260)
2026-08-08
Rank Moved
Rank dropped 668 spots (#513 → #1181)
2026-08-06
Rank Moved
Rank dropped 45 spots (#467 → #512)
2026-08-03
Newly Listed
First tracked at rank #467

Embed Badge Badge guide for maintainers →

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

Other agents in Agent Frameworks

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.3 · Raw JSON