llm-for-zotero

An open-source research agent system for your Zotero library.

Research & Data TypeScript Grade C Listed AGPL-3.0
56.8/100
Rank #713 of 1328
Compare llm-for-zotero

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-09-20 · 1d ago
Recent change
No recent signal change

Is llm-for-zotero safe? llm-for-zotero scores 56.8/100 (Grade C), ranked #713 of 1328 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; 2% of recent commits are signed; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Research & Data

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-12
Rank Moved
Rank dropped 11 spots (#708 → #719)
2026-09-08
Rank Moved
Rank dropped 15 spots (#690 → #705)
2026-09-07
Rank Moved
Rank dropped 43 spots (#647 → #690)
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.
81.3
Activity sub-score · out of 100
#15

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-09-21 06:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-09-21

Activity & Reach

Stars
3.1k
Forks
175
Last Push
2026-09-20
yesterday
Commits (4 wk)
580
Downloads (7d)
HN mentions (30d)
Open Issues
155
Rank Change
▲2
was #715

Analysis

HVTrust Dimensions vs Research & Data

56.8 / 100 · 100.0% confidence

llm-for-zotero Research & Data average (33 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.5 / 25
2.7 below avg 8.2
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.1 below avg 11.9
Transparency50% declared license · 50% OSSF Scorecard
12.2 / 17
in line with avg 11.8
Maintenance60% last-push freshness · 40% commit activity
19.9 / 20
7.1 above avg 12.8
AdoptionLog-scaled stars · package downloads
8.4 / 20
2.5 below avg 10.9

Activity Inputs

81.3 / 100
StarsRepository reach
20.9 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
10.4 / 20

Supply Chain Trust

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

Is llm-for-zotero safe?

llm-for-zotero 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 llm-for-zotero publish package provenance?
No published build provenance is currently detected for llm-for-zotero. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does llm-for-zotero have an OpenSSF Scorecard?
llm-for-zotero 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 llm-for-zotero actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does llm-for-zotero use?
llm-for-zotero ships under AGPL-3.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are llm-for-zotero's commits signed?
2% of the last 100 commits to llm-for-zotero 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
medium confidence
Declared
MCP support appears present, but direct server implementation is less certain.
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 llm-for-zotero?

For maintainers

HVTrust scores llm-for-zotero 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 17Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-12
Rank Moved
Rank dropped 11 spots (#708 → #719)
2026-09-08
Rank Moved
Rank dropped 15 spots (#690 → #705)
2026-09-07
Rank Moved
Rank dropped 43 spots (#647 → #690)
2026-09-06
Rank Moved
Rank dropped 19 spots (#628 → #647)
2026-09-05
Rank Moved
Rank dropped 75 spots (#553 → #628)
2026-09-04
Rank Moved
Rank dropped 20 spots (#533 → #553)
2026-09-03
Rank Moved
Rank dropped 30 spots (#503 → #533)
2026-09-02
Rank Moved
Rank dropped 18 spots (#485 → #503)
2026-09-01
Rank Moved
Rank dropped 10 spots (#475 → #485)
2026-08-31
Rank Moved
Rank dropped 28 spots (#447 → #475)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.3/10
2026-08-29
Grade Changed
Trust grade D → C
2026-08-29
Rank Moved
Rank rose 578 spots (#1033 → #455)
2026-08-29
HVTrust Changed
HVTrust up 33.1pts (23.9 → 57.0)
2026-08-28
Rank Moved
Rank dropped 37 spots (#996 → #1033)
2026-08-27
Rank Moved
Rank dropped 22 spots (#974 → #996)
2026-08-26
Rank Moved
Rank dropped 100 spots (#874 → #974)
2026-08-16
Rank Moved
Rank dropped 13 spots (#871 → #884)
2026-08-10
Rank Moved
Rank dropped 45 spots (#823 → #868)
2026-08-08
Rank Moved
Rank dropped 357 spots (#460 → #817)
2026-08-06
Newly Listed
First tracked at rank #474

Embed Badge Badge guide for maintainers →

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

Other agents in Research & Data

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