Is brick-tq-shacl safe to use?

brick-tq-shacl has no known vulnerabilities on the latest version (0.4.1). DepScope rates its health at 55/100 (high risk).

What is the latest version of brick-tq-shacl?

The latest version of brick-tq-shacl is 0.4.1, released 2025-11-23.

Does brick-tq-shacl have known vulnerabilities?

No known vulnerabilities on the latest version of brick-tq-shacl.

Is brick-tq-shacl deprecated?

No, brick-tq-shacl is actively maintained. Latest release: 0.4.1 (2025-11-23).

What are alternatives to brick-tq-shacl?

Popular alternatives to brick-tq-shacl in PyPI include: boto3, packaging, idna, urllib3, requests.

What license does brick-tq-shacl use?

brick-tq-shacl is licensed under BSD-3-Clause.

brick-tq-shacl

pypiv0.4.1

Wraps topquadrant's SHACL implementation in a simple Python wrapper to be API-compatible with pySHACL

License BSD-3-Clausepermissive44 versions5 deps243 weekly dl

/ 100

Health

use with caution

[email protected] low health (55/100) — consider alternatives

Moderate health score (55/100) — verify manually

Health breakdown0 – 100

15/25

maintenance

3/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (5)

pyontoenv pytqshacl[cli]rdflib requests pytest

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/brick-tq-shacl