updated 2026-09-08 19:33 UTC

Ip As Logo Skill

s1dashu/ip-as-logo-skill

A compact Agent Skill for highly simplified, rounded, subtly neo-skeuomorphic IP mascot logos.

Agent Skills Grade D Listed MIT
22.8/100
Rank #331 of 351
Compare Ip As Logo Skill

How does it stack up against its Agent Skills 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 D · 1/5 signals
Last push
2026-08-22 · 17d ago
Recent change
New

Is Ip As Logo Skill safe? Ip As Logo Skill scores 22.8/100 (Grade D), ranked #331 of 351 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 13% of recent commits are signed; last pushed 2026-08-22. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Agent Skills

#329 Shuohao Skills — 23.1 (D) → #330 Anti Slop — 23.0 (D) → #332 Shinkoku — 22.2 (D) → #333 Autoprompt Skill — 21.9 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-08
Newly Listed
First tracked at rank #331
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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 Ip As Logo Skill View Agent Skills Report missing data
74.6
Activity sub-score · out of 100
#331
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-08 19:33 UTC · Repo last pushed 17 days ago

Activity & Reach

Stars
5.1k
Forks
256
Last Push
2026-08-22
17 days ago
Commits (4 wk)
30
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
5
Rank Change
NEW

Analysis

HVTrust Dimensions vs Agent Skills

22.8 / 100 · 50.0% confidence

Ip As Logo Skill Agent Skills average (351 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.7 / 25
6.7 below avg 7.4
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.3 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
16.8 / 20
2.4 above avg 14.4
AdoptionLog-scaled stars · package downloads
8.9 / 20
in line with avg 8.8

Activity Inputs

74.6 / 100
StarsRepository reach
22.2 / 30
FreshnessLast push recency
22.6 / 25
ActivityRecent commits
18.6 / 25
CommunityFork signal
11.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
13%
of last 100 commits verified

Is Ip As Logo Skill safe?

Public trust evidence for Ip As Logo Skill 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 Ip As Logo Skill publish package provenance?
No published build provenance is currently detected for Ip As Logo Skill. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Ip As Logo Skill have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for Ip As Logo Skill. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Ip As Logo Skill actively maintained?
Maintained. Last push was 17 days ago.
What license does Ip As Logo Skill use?
Ip As Logo Skill ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Ip As Logo Skill's commits signed?
13% of the last 100 commits to Ip As Logo Skill 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 Ip As Logo Skill?

For maintainers

HVTrust scores Ip As Logo Skill 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
Listed 1
2026-09-08
Newly Listed
First tracked at rank #331
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 22.8 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/ip-as-logo-skill.svg)](https://hvtracker.net/agents/ip-as-logo-skill)
HTML:
<a href="https://hvtracker.net/agents/ip-as-logo-skill"><img src="https://hvtracker.net/badge/ip-as-logo-skill.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON