Srcbook

TypeScript-centric app development platform: notebook and AI app builder

UI & App Builders TypeScript Grade C Listed Apache-2.0
51.2/100
Rank #303 of 468
Compare Srcbook

How does it stack up against its UI & App Builders 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-07-30 · 7d ago
Recent change
No recent signal change

Is Srcbook safe? Srcbook scores 51.2/100 (Grade C), ranked #303 of 468 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.0/10; 88% of recent commits are signed; last pushed 2026-07-30. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in UI & App Builders

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-07-29
Activity Resumed
Activity resumed
2026-07-29
Grade Changed
Trust grade D → C
2026-07-29
Rank Moved
Rank rose 48 spots (#355 → #307)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.0/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.
63.0
Activity sub-score · out of 100
#12

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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-08-06 02:30 UTC · Repo last pushed 7 days ago

Rank Trend

2026-07-05 2026-08-06

Activity & Reach

Stars
3.4k
Forks
312
Last Push
2026-07-30
7 days ago
Commits (4 wk)
2
Downloads (7d)
HN mentions (30d)
Open Issues
29
Rank Change
=
was #303

Analysis

HVTrust Dimensions vs UI & App Builders

51.2 / 100 · 100.0% confidence

Srcbook UI & App Builders average (15 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.2 / 25
3.1 below avg 11.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.9 below avg 12.7
Transparency50% declared license · 50% OSSF Scorecard
11.1 / 17
1.2 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.4 / 20
3.6 below avg 17.0
AdoptionLog-scaled stars · package downloads
8.5 / 20
4.5 below avg 13.0

Activity Inputs

63.0 / 100
StarsRepository reach
21.2 / 30
FreshnessLast push recency
24.0 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
11.6 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
3.0 / 10
OpenSSF Scorecard · scanned Jul 11, 2026 (refresh pending)
Signed Commits
88%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 5
CI-Tests 0
CII-Best-Practices 0
Code-Review 2
Contributors 10
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Srcbook safe?

Public trust evidence for Srcbook 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 Srcbook publish package provenance?
No published build provenance is currently detected for Srcbook. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Srcbook have an OpenSSF Scorecard?
Srcbook has an OpenSSF Scorecard score of 3.0/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 Srcbook actively maintained?
Actively maintained. The repository was pushed to within the last 7 day(s).
What license does Srcbook use?
Srcbook ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Srcbook's commits signed?
88% of the last 100 commits to Srcbook 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: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • code
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 Srcbook'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-07-29
Activity Resumed
Activity resumed
2026-07-05
Activity Went Stale
No commits for 90 days

Maintain Srcbook?

For maintainers

HVTrust scores Srcbook 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 8HVTrust 2Listed 1Scorecard 1Stale 1Score 1Grade 1Fresh 1
2026-07-29
Activity Resumed
Activity resumed
2026-07-29
Grade Changed
Trust grade D → C
2026-07-29
Rank Moved
Rank rose 48 spots (#355 → #307)
2026-07-29
HVTrust Changed
HVTrust up 8.7pts (42.3 → 51.0)
2026-07-29
Activity Score Changed
Activity score up 20pts (42 → 62)
2026-07-15
Rank Moved
Rank dropped 26 spots (#320 → #346)
2026-07-14
Rank Moved
Rank dropped 18 spots (#302 → #320)
2026-07-13
Rank Moved
Rank dropped 34 spots (#268 → #302)
2026-07-05
Activity Went Stale
No commits for 90 days
2026-06-24
Rank Moved
Rank dropped 31 spots (#229 → #260)
2026-06-23
Rank Moved
Rank dropped 18 spots (#211 → #229)
2026-06-22
Rank Moved
Rank dropped 10 spots (#201 → #211)
2026-06-21
Scorecard Added
OSSF Scorecard: 3.1/10
2026-06-21
Rank Moved
Rank rose 59 spots (#260 → #201)
2026-06-21
HVTrust Changed
HVTrust up 26.0pts (19.6 → 45.6)
2026-06-20
Newly Listed
First tracked at rank #260

Embed Badge Badge guide for maintainers →

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

Other agents in UI & App Builders

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