updated 2026-10-05 00:09 UTC

Lieflat Charts

Repository

Data visualization Skill for AI Agents, turning data into polished, interactive HTML charts. 面向 AI Agents 的数据可视化 Skill，将数据快速生成精致、可交互的 HTML 图表。

Agent Skills HTML Listed NOASSERTION Source-available

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

OSSF Scorecard 2.5 / 10
Provenance None
Signed commits 22%
Last push 30d ago
Compare Lieflat Charts

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Lieflat Charts scores 46.6/100 (Grade D), ranked #283 of 359 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 2.5/10; 22% of recent commits are signed; last pushed 2026-09-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How Lieflat Charts 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 Lieflat Charts 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/larashero3-dotcom/lieflat-charts, NOASSERTION, last pushed 2026-09-05. 22% 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 2.5/10 (scanned Oct 2, 2026). The checks that decide who can get a change released:

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

  3. Published packages None

    No registry package. Lieflat Charts 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-10-02 OSSF Scorecard: 2.5/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 Lieflat Charts’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 Lieflat Charts compares in Agent Skills

  1. #281 Skill Based Architecture 46.6 ±0
  2. #282 PPT Design Skill 46.6 ±0
  3. #283 Lieflat Charts 46.6 this agent
  4. #284 Claude Skills Marketplace 46.5 −0.1
  5. #285 Fable Method 46.4 −0.2

Bars show each HVTrust score; the tick marks Lieflat Charts’s 46.6.

Where the 46.6 comes from

HVTrust dimensions vs the Agent Skills average

46.6 / 100 · 100.0% confidence

Lieflat Charts Agent Skills average (359 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.2 / 25
3.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
10.6 / 17
1.6 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
11.9 / 20
2.2 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-03
Rank Moved
Rank dropped 26 spots (#256 → #282)
2026-10-03
Activity Score Changed
Activity score down 7pts (68 → 62)
2026-10-02
Scorecard Added
OSSF Scorecard: 2.5/10
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.5/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.
Compare with another agent Get email alerts for Lieflat Charts View Agent Skills Report missing data
61.5
Activity sub-score · out of 100
#283
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-05 00:09 UTC · Repo last pushed 30 days ago

Rank Trend

2026-09-29 2026-10-04

Activity & Reach

Stars
5.9k
Forks
363
Last Push
2026-09-05
30 days ago
Commits (4 wk)
2
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
1
Rank Change
=
was #283

Analysis

Activity Inputs

61.5 / 100
StarsRepository reach
22.6 / 30
FreshnessLast push recency
20.8 / 25
ActivityRecent commits
6.0 / 25
CommunityFork signal
11.9 / 20

Common questions about Lieflat Charts

Source-available software. A lower HVTrust score reflects fewer public supply-chain artifacts (open license, build provenance, signed commits) — not a security finding. Lieflat Charts may have internal security practices not visible through public signals.
Public trust evidence for Lieflat Charts 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 Lieflat Charts publish package provenance?
No published build provenance is currently detected for Lieflat Charts. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Lieflat Charts have an OpenSSF Scorecard?
Lieflat Charts has an OpenSSF Scorecard score of 2.5/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 Lieflat Charts actively maintained?
Maintained. Last push was 30 days ago.
What license does Lieflat Charts use?
Lieflat Charts ships under NOASSERTION. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Lieflat Charts's commits signed?
22% of the last 100 commits to Lieflat Charts 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
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 Lieflat Charts?

For maintainers

HVTrust scores Lieflat Charts 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 2Listed 1HVTrust 1Scorecard 1Score 1
2026-10-03
Rank Moved
Rank dropped 26 spots (#256 → #282)
2026-10-03
Activity Score Changed
Activity score down 7pts (68 → 62)
2026-10-02
Scorecard Added
OSSF Scorecard: 2.5/10
2026-10-02
Rank Moved
Rank rose 101 spots (#357 → #256)
2026-10-02
HVTrust Changed
HVTrust up 26.9pts (21.9 → 48.8)
2026-09-29
Newly Listed
First tracked at rank #354
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 46.6 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/lieflat-charts.svg)](https://hvtracker.net/agents/lieflat-charts)
HTML:
<a href="https://hvtracker.net/agents/lieflat-charts"><img src="https://hvtracker.net/badge/lieflat-charts.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