Is Blinker Safe?

Blinker — Nerq Trust Score 67.5/100 (B- grade). Based on analysis of 2 trust dimensions, it is generally safe but has some concerns. Last updated: 2026-03-31.

Use Blinker with some caution. Blinker is a Python package with a Nerq Trust Score of 67.5/100 (B-), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 90/100. Popularity: 100/100. Data sourced from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. Last updated: 2026-03-31. Machine-readable data (JSON).

Is Blinker safe?

CAUTION — Blinker has a Nerq Trust Score of 67.5/100 (B-). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

Security Analysis → {name} Privacy Report →

What is Blinker's trust score?

Blinker has a Nerq Trust Score of 67.5/100, earning a B- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
100

What are the key security findings for Blinker?

Blinker's strongest signal is popularity at 100/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 100/100 — community adoption

What is Blinker and who maintains it?

AuthorJason Kirtland
Categorypypi
SourceN/A

Blinker Across Platforms

Same developer/company in other registries:

blinker
55/100 · crates

Similar Pypi by Trust Score

backoff (78)aiofile (77)asana (77)allure-pytest (77)catboost (77)
See all safest Pypi →

Safety Guide: Blinker

What is Blinker?

Blinker is a Python package — Fast, simple object-to-object and broadcast signaling.

How to Verify Safety

Run pip audit or safety check. Review on PyPI for download stats.

You can also check the trust score via API: GET /v1/preflight?target=blinker

Key Safety Concerns for Python packages

When evaluating any Python package, watch for: dependency vulnerabilities, malicious uploads, maintenance status.

Trust Assessment

Blinker has a Nerq Trust Score of 68/100 (B-) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Detailed Score Analysis

DimensionScore
Security90/100
Privacy80/100
Reliability90/100
Transparency50/100
Maintenance60/100

Based on 5 dimensions. Data from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard.

What data does Blinker collect?

Blinker is a Python package maintained by Jason Kirtland. It receives approximately 37,134,709 weekly downloads.

As a development package, Blinker does not directly collect end-user personal data. However, applications built with it may collect data depending on implementation. Privacy score: 80/100.

Review the package's dependencies for potential supply chain risks. Run your package manager's audit command regularly.

Full analysis: Blinker Privacy Report · Privacy review

Is Blinker secure?

Security score: 90/100. Blinker has 0 known vulnerabilities (CVEs) in the National Vulnerability Database. This is a clean record.

License information not available. Open-source packages allow independent security review of the source code.

Run your package manager's audit command (`npm audit`, `pip audit`, `cargo audit`) to check for known vulnerabilities in your dependency tree.

Full analysis: Blinker Security Report

Blinker Across Platforms

Same developer/company in other registries:

blinker (crates, 55/100)

How we calculated this score

Blinker's trust score of 67.5/100 (B-) is computed from PyPI registry, GitHub repository, NVD, OSV.dev, and OpenSSF Scorecard. The score reflects 5 independent dimensions: security (90/100), privacy (80/100), reliability (90/100), transparency (50/100), maintenance (60/100). Each dimension is weighted equally to produce the composite trust score.

Nerq analyzes over 7.5 million entities across 26 registries using the same methodology, enabling direct cross-entity comparison. Scores are updated continuously as new data becomes available.

This page was last reviewed on March 31, 2026. Data version: 1.0.

Full methodology documentation · Machine-readable data (JSON API)

Frequently Asked Questions

Is Blinker safe to use?
Use with some caution. blinker has a Nerq Trust Score of 67.5/100 (B-). Strongest signal: popularity (100/100). Score based on security (90/100), popularity (100/100).
What is Blinker's trust score?
blinker: 67.5/100 (B-). Score based on: security (90/100), popularity (100/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=blinker
What are safer alternatives to Blinker?
In the pypi category, more Python packages are being analyzed — check back soon. blinker scores 67.5/100.
Does Blinker have known vulnerabilities?
Nerq checks Blinker against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
How actively maintained is Blinker?
Blinker has a trust score of 67.5/100 (B-). Below Nerq Verified threshold — conduct additional review.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.