img2threejs

Rebuild the object in a reference image as a code-only, procedural, quality-gated, animation-ready Three.js model. Token-efficient image-to-3D.

Agent Skills Python Listed Apache-2.0

Is img2threejs safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.3 / 10
Provenance None
Signed commits 33%
Last push 6d ago
Compare img2threejs
Suggest a correction

In detail: img2threejs scores 56.3/100 (Grade C), ranked #167 of 396 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 4.3/10; 33% of recent commits are signed; last pushed 2026-11-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How img2threejs 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.

Chain of custody

Scanners check what the code says. This traces who ships img2threejs 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/img2threejs/img2threejs, Apache-2.0, last pushed 2026-11-16. 33% 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.3/10 (scanned Nov 20, 2026). The checks that decide who can get a change released:

    • Code Review3
    • Branch Protection5
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies5
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 3
    Contributors 6
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 5
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages None

    No registry package. img2threejs 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-11 OSSF Scorecard: 3.7/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 img2threejs’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.

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 img2threejs compares in Agent Skills

  1. #165 Claude Code Hooks 56.5 +0.2
  2. #166 Rampstackco Claude Skills 56.4 +0.1
  3. #167 img2threejs 56.3 this agent
  4. #168 Maestro Orchestrate 56.2 −0.1
  5. #169 Aaron Marketing Skills 56.1 −0.2

Bars show each HVTrust score; the tick marks img2threejs’s 56.3.

Where the 56.3 comes from

HVTrust dimensions vs the Agent Skills average

56.3 / 100 · 100.0% confidence

img2threejs Agent Skills average (396 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
7.0 / 25
1.3 below avg 8.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.7 below avg 11.5
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
15.9 / 20
2.0 above avg 13.9
AdoptionLog-scaled stars · package downloads
10.4 / 20
1.2 above avg 9.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-06
Rank Moved
Rank rose 36 spots (#185 → #149)
2026-11-05
Rank Moved
Rank rose 15 spots (#200 → #185)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.3/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.
78.9
Activity sub-score · out of 100
#167

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-11-22 12:09 UTC · Repo last pushed 6 days ago

Rank Trend

2026-10-01 2026-11-22

Activity & Reach

Stars
21.7k
Forks
1.8k
Last Push
2026-11-16
6 days ago
Commits (4 wk)
11
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
81
Rank Change
=
was #167

Analysis

Activity Inputs

78.9 / 100
StarsRepository reach
26.0 / 30
FreshnessLast push recency
24.2 / 25
ActivityRecent commits
13.5 / 25
CommunityFork signal
15.2 / 20

Common questions about img2threejs

img2threejs has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does img2threejs publish package provenance?
No published build provenance is currently detected for img2threejs. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does img2threejs have an OpenSSF Scorecard?
img2threejs has an OpenSSF Scorecard score of 4.3/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 img2threejs actively maintained?
Actively maintained. The repository was pushed to within the last 6 day(s).
What license does img2threejs use?
img2threejs ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are img2threejs's commits signed?
33% of the last 100 commits to img2threejs 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 img2threejs?

For maintainers

HVTrust scores img2threejs 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 7Listed 1HVTrust 1Grade 1Scorecard 1
2026-11-06
Rank Moved
Rank rose 36 spots (#185 → #149)
2026-11-05
Rank Moved
Rank rose 15 spots (#200 → #185)
2026-10-21
Rank Moved
Rank rose 10 spots (#202 → #192)
2026-10-17
Rank Moved
Rank dropped 15 spots (#184 → #199)
2026-10-16
Rank Moved
Rank rose 16 spots (#200 → #184)
2026-10-13
Rank Moved
Rank rose 28 spots (#222 → #194)
2026-10-11
Scorecard Added
OSSF Scorecard: 3.7/10
2026-10-11
Grade Changed
Trust grade D → C
2026-10-11
Rank Moved
Rank rose 146 spots (#365 → #219)
2026-10-11
HVTrust Changed
HVTrust up 29.7pts (22.1 → 51.8)
2026-10-01
Newly Listed
First tracked at rank #353

Embed Badge Badge guide for maintainers →

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