updated 2026-10-15 04:08 UTC

Fireworks Tech Graph

Repository Website

Generate production-quality SVG+PNG technical diagrams from natural language. 7 styles, UML support, and AI/Agent workflow patterns.

Agent Skills Python Listed MIT

Is Fireworks Tech Graph safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.4 / 10
Provenance None
Signed commits 35%
Last push 40d ago
Advisories None known
Compare Fireworks Tech Graph

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Fireworks Tech Graph scores 54.9/100 (Grade C), ranked #175 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 4.4/10; 35% of recent commits are signed; no published advisory affects its latest release (@yizhiyanhua-ai/fireworks-tech-graph); last pushed 2026-09-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Fireworks Tech Graph 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 Fireworks Tech Graph 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/yizhiyanhua-ai/fireworks-tech-graph, MIT, last pushed 2026-09-05. 35% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

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

    • Code Review4
    • Branch Protection0
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies8
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 1
    CII-Best-Practices 0
    Code-Review 4
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 8
    SAST 0
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 10

  3. Published packages Linked, not attested

    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: @yizhiyanhua-ai/fireworks-tech-graph 1.0.4. No published advisory affects it (OSV, checked 2026-10-15).

Changes to this chain

  • 2026-09-10 OSSF Scorecard: 4.4/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 Fireworks Tech Graph’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 Fireworks Tech Graph compares in Agent Skills

  1. #173 Brooks Lint 54.9 ±0
  2. #174 Tinybase 54.9 ±0
  3. #175 Fireworks Tech Graph 54.9 this agent
  4. #176 Android Skills 54.8 −0.1
  5. #177 Feishu Docx 54.8 −0.1

Bars show each HVTrust score; the tick marks Fireworks Tech Graph’s 54.9.

Where the 54.9 comes from

HVTrust dimensions vs the Agent Skills average

54.9 / 100 · 100.0% confidence

Fireworks Tech Graph Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.2 / 25
0.8 below avg 8.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.1
Maintenance60% last-push freshness · 40% commit activity
9.3 / 20
4.8 below avg 14.1
AdoptionLog-scaled stars · package downloads
11.4 / 20
2.4 above 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-05
Rank Moved
Rank dropped 18 spots (#139 → #157)
2026-09-25
Rank Moved
Rank dropped 22 spots (#106 → #128)
2026-09-23
Grade Changed
Trust grade D → C
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.4/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 40 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for Fireworks Tech Graph View Agent Skills Report missing data
57.8
Activity sub-score · out of 100
#175
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 C 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-15 04:08 UTC · Repo last pushed 40 days ago

Rank Trend

2026-09-29 2026-10-15

Activity & Reach

Stars
11.7k
Forks
930
Last Push
2026-09-05
40 days ago
Commits (4 wk)
0
Downloads (7d)
16
npm
HN mentions (30d)
—
Open Issues
1
Rank Change
▼1
was #174

Analysis

Activity Inputs

57.8 / 100
StarsRepository reach
24.4 / 30
FreshnessLast push recency
19.4 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
13.8 / 20

Common questions about Fireworks Tech Graph

Public trust evidence for Fireworks Tech Graph 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 Fireworks Tech Graph publish package provenance?
No published build provenance is currently detected for Fireworks Tech Graph. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Fireworks Tech Graph have an OpenSSF Scorecard?
Fireworks Tech Graph has an OpenSSF Scorecard score of 4.4/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 Fireworks Tech Graph actively maintained?
Slowing down. Last push was 40 days ago — keep an eye on whether activity resumes.
What license does Fireworks Tech Graph use?
Fireworks Tech Graph ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Fireworks Tech Graph's commits signed?
34% of the last 100 commits to Fireworks Tech Graph 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
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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

Maintain Fireworks Tech Graph?

For maintainers

HVTrust scores Fireworks Tech Graph 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 15HVTrust 4Listed 2Grade 2Scorecard 1Delisted 1
2026-10-05
Rank Moved
Rank dropped 18 spots (#139 → #157)
2026-09-25
Rank Moved
Rank dropped 22 spots (#106 → #128)
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 178 spots (#282 → #104)
2026-09-23
HVTrust Changed
HVTrust up 30.3pts (28.7 → 59.0)
2026-09-22
Newly Listed
First tracked at rank #282
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-14
Rank Moved
Rank rose 13 spots (#102 → #89)
2026-09-10
Scorecard Added
OSSF Scorecard: 4.4/10
2026-09-10
Grade Changed
Trust grade D → C
2026-09-10
Rank Moved
Rank rose 199 spots (#298 → #99)
2026-09-10
HVTrust Changed
HVTrust up 24.3pts (34.2 → 58.5)
2026-09-06
Rank Moved
Rank dropped 10 spots (#270 → #280)
2026-09-05
Rank Moved
Rank rose 37 spots (#307 → #270)
2026-09-05
HVTrust Changed
HVTrust up 14.0pts (21.8 → 35.8)
2026-09-03
Rank Moved
Rank dropped 50 spots (#251 → #301)
2026-09-03
HVTrust Changed
HVTrust down 12.4pts (34.2 → 21.8)
2026-09-02
Rank Moved
Rank dropped 13 spots (#238 → #251)
2026-09-01
Rank Moved
Rank dropped 13 spots (#225 → #238)
2026-08-31
Rank Moved
Rank dropped 19 spots (#206 → #225)
2026-08-30
Rank Moved
Rank dropped 35 spots (#171 → #206)
2026-08-29
Rank Moved
Rank dropped 40 spots (#131 → #171)
2026-08-28
Rank Moved
Rank dropped 28 spots (#103 → #131)
2026-08-27
Rank Moved
Rank dropped 20 spots (#83 → #103)
2026-08-26
Newly Listed
First tracked at rank #83
GitHub → Website → npm: @yizhiyanhua-ai/fireworks-tech-graph

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/fireworks-tech-graph.svg)](https://hvtracker.net/agents/fireworks-tech-graph)
HTML:
<a href="https://hvtracker.net/agents/fireworks-tech-graph"><img src="https://hvtracker.net/badge/fireworks-tech-graph.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