Is Notebooklm Py safe to use?

Notebooklm Py has an HVTrust score of 89.3/100 (Grade A), ranked #3 of 371 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Notebooklm Py?

Notebooklm Py scores 89.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 19.7k GitHub stars and is categorized under Agent Skills.

Notebooklm Py

Repository

Unofficial Python API and agentic skill for Google Gemini Notebook. Full programmatic access to NotebookLM's features—including capabilities the web UI doesn't expose—via Python, CLI, and AI agents like Claude Code, Codex, and OpenClaw.

Agent Skills Python Listed MIT

Is Notebooklm Py safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.3 / 10

Provenance Attested

Signed commits 56%

Last push today

Advisories None known

Compare Notebooklm Py

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Notebooklm Py scores 89.3/100 (Grade A), ranked #3 of 371 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.3/10; 56% of recent commits are signed; no published advisory affects its latest release (notebooklm-py); last pushed 2026-10-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Notebooklm Py 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.

Raise the OSSF Scorecard from 6.3 to 9.0lowest checks: CII-Best-Practices 0, Code-Review 0, Fuzzing 0 +3.9 → 93.2 A · #1 of 371
Sign every commit56% signed today +1.5 → 90.8 A · #2 of 371

Already done? Suggest a correction Add the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Notebooklm Py 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.

Source Partly signed

github.com/teng-lin/notebooklm-py, MIT, last pushed 2026-10-10. 56% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
Review and release Mixed

OpenSSF Scorecard rates the repository's practices 6.3/10 (scanned Oct 7, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies4
All 18 Scorecard checks

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 6

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 4

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10
Published packages Linked and attested
- PyPI notebooklm-py Source link points back to this repo Build provenance attested
What you install today No known advisories

Latest release checked: notebooklm-py 0.8.4. No published advisory affects it (OSV, checked 2026-10-10).

Changes to this chain

2026-09-23 Package provenance attestation detected
2026-09-03 OSSF Scorecard: 6.8/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 Notebooklm Py’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 Notebooklm Py compares in Agent Skills

Bars show each HVTrust score; the tick marks Notebooklm Py’s 89.3.

Where the 89.3 comes from

HVTrust dimensions vs the Agent Skills average

89.3 / 100 · 100.0% confidence

Notebooklm Py Agent Skills average (371 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

18.2 / 25

10.4 above avg 7.8

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

6.6 above avg 11.4

Transparency50% declared license · 50% OSSF Scorecard

13.9 / 17

1.9 above avg 12.0

Maintenance60% last-push freshness · 40% commit activity

18.6 / 20

4.5 above avg 14.1

AdoptionLog-scaled stars · package downloads

16.4 / 20

7.4 above avg 9.0

Quick Trust Read

What Would Improve It

Improve safety / integrity to lift the weakest part of the trust profile.

Recent Changes

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 6.3/10. Tighten the weakest checks to improve public safety evidence.

Compare with OmniRoute Get email alerts for Notebooklm Py View Agent Skills Report missing data

87.2

Activity sub-score · out of 100

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 A 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 →

Rank Trend

2026-09-29 2026-10-10

Activity & Reach

Stars

19.7k

Forks

2.6k

Last Push

2026-10-10

today

Commits (4 wk)

Downloads (7d)

38,642

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #4

Analysis

Activity Inputs

87.2 / 100

StarsRepository reach

25.8 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

20.5 / 25

CommunityFork signal

15.9 / 20

Common questions about Notebooklm Py

Public supply-chain signals for Notebooklm Py are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Notebooklm Py carries less obvious unverified-evidence risk than projects with thin signals.

Does Notebooklm Py publish package provenance?

Yes. Notebooklm Py's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Notebooklm Py have an OpenSSF Scorecard?

Notebooklm Py has an OpenSSF Scorecard score of 6.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 Notebooklm Py actively maintained?

Actively maintained. The repository was pushed to within the last 1 day(s).

What license does Notebooklm Py use?

Notebooklm Py ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Notebooklm Py's commits signed?

56% of the last 100 commits to Notebooklm Py 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.

Compare Notebooklm Py head-to-head

Notebooklm Py vs OmniRoute → Notebooklm Py vs Vercel Skills → Notebooklm Py vs Larksuite Cli →

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

high confidence

Implemented

Notebooklm Py appears to expose MCP server capabilities.

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

high confidence

1 tags

Broad capability areas detected.

browser

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

How this surface has changed

Detected changes to Notebooklm Py's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Notebooklm Py?

For maintainers

HVTrust scores Notebooklm Py 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

2026-09-24

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → A

2026-09-23

Rank Moved

Rank rose 184 spots (#189 → #5)

2026-09-23

HVTrust Changed

HVTrust up 51.5pts (35.7 → 87.2)

2026-09-22

Newly Listed

First tracked at rank #189

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-03

Scorecard Added

OSSF Scorecard: 6.8/10

2026-09-03

Grade Changed

Trust grade B → A

2026-09-03

HVTrust Changed

HVTrust up 13.4pts (78.7 → 92.1)

2026-08-26

Newly Listed

First tracked at rank #5

GitHub → PyPI: notebooklm-py

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/notebooklm-py.svg)](https://hvtracker.net/agents/notebooklm-py)
            
HTML:
            <a href="https://hvtracker.net/agents/notebooklm-py"><img src="https://hvtracker.net/badge/notebooklm-py.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON

Notebooklm Py

How Notebooklm Py could raise its score

Chain of custody

Source Partly signed

Review and release Mixed

Published packages Linked and attested

What you install today No known advisories

Changes to this chain

Evidence behind this score

Verify this score yourself

What this score doesn’t check

How Notebooklm Py compares in Agent Skills

Where the 89.3 comes from

HVTrust dimensions vs the Agent Skills average

Quick Trust Read

Rank Trend

Activity & Reach

Analysis

Activity Inputs

Common questions about Notebooklm Py

Compare Notebooklm Py head-to-head

AI agent surface

Maintain Notebooklm Py?

Reputation Timeline

Embed Badge Badge guide for maintainers →

Other agents in Agent Skills