Is @graphy-dev/content.trig.read safe to use?

@graphy-dev/content.trig.read has no known vulnerabilities on the latest version (0.0.41). DepScope rates its health at 39/100 (critical risk).

What is the latest version of @graphy-dev/content.trig.read?

The latest version of @graphy-dev/content.trig.read is 0.0.41, released 2019-12-11.

Does @graphy-dev/content.trig.read have known vulnerabilities?

No known vulnerabilities on the latest version of @graphy-dev/content.trig.read.

Is @graphy-dev/content.trig.read deprecated?

No, @graphy-dev/content.trig.read is actively maintained. Latest release: 0.0.41 (2019-12-11).

What are alternatives to @graphy-dev/content.trig.read?

Popular alternatives to @graphy-dev/content.trig.read in npm include: ?, semver, minimatch, debug, brace-expansion.

What license does @graphy-dev/content.trig.read use?

@graphy-dev/content.trig.read is licensed under ISC.

@graphy-dev/content.trig.read

npmv0.0.41

Single-threaded RDF TriG content reader

License ISCpermissive20 versions1 maintainers3 deps54 weekly dl

blake-regalia/graphy.js

/ 100

Health

use with caution

@graphy-dev/[email protected] low health (39/100) — consider alternatives

Moderate health score (39/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Bundle & TypeScript

🌟

TypeScript

0/10untyped

No type definitions available

Health History

Dependency Tree

License Audit

Dependencies (3)

@graphy-dev/core.data.factory @graphy-dev/core.iso.stream uri-js

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/npm/@graphy-dev/content.trig.read