stardog

v6.0.0

Stardog JavaScript Framework for node.js and the browser - Develop apps using the Stardog RDF Database & JS. For more information about how to use this package see README

Latest version published 7 months ago

License: Apache-2.0

NPM

GitHub

Package Health Score

62 / 100

security
No known security issues
popularity
Limited
maintenance
Sustainable
community
Sustainable

Explore Similar Packages

Security

No known security issues

All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions

Version				Vulnerabilities	License Risk
6.0.0	\|	04/2024	Popular	0 C 0 H 0 M 0 L	0 H 0 M 0 L
5.3.1	\|	01/2024		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.8.0	\|	03/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
4.9.0	\|	03/2023		0 C 0 H 0 M 0 L	0 H 0 M 0 L
3.7.0	\|	12/2022		0 C 0 H 0 M 0 L	0 H 0 M 0 L

License

Apache-2.0

Security Policy

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Limited

Weekly Downloads (241)

GitHub Stars: 78
Forks: 32
Contributors: 30

Direct Usage Popularity

The npm package stardog receives a total of 241 downloads a week. As such, we scored stardog popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package stardog, we found that it has been starred 78 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 30
Funding: No

With more than 10 contributors for the stardog repository, this is possibly a sign for a growing and inviting community.

We found a way for you to contribute to the project! Looks like stardog is missing a Code of Conduct.

Embed Package Health Score Badge

Maintenance

Sustainable

Commit Frequency

Open Issues: 11
Open PR: 0
Last Release: 7 months ago
Last Commit: 7 months ago

Further analysis of the maintenance status of stardog based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that stardog demonstrates a positive version release cadence with at least one new version released in the past 12 months.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Keep your project healthy

Check your package.json

Ensure all the packages you're using are healthy and well-maintained

Snyk Vulnerability Scanner

Get health score & security insights directly in your IDE

Package

Node.js Compatibility: >=6.0.0

Age: 12 years
Dependencies: 6 Direct
Versions: 69
Install Size: 378 kB
Dist-tags: 1
# of Files: 34
Maintainers: 3
TS Typings: Yes

stardog has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

Not sure how to use stardog?

To help you get started, we've collected the most common ways that stardog is being used within popular public projects.

mark-watson / javascript_intelligent_systems / src / stardog_semantic_web.js View on Github

// @flow

var stardog = require("stardog");

var i, conn = new stardog.Connection();

conn.setEndpoint("http://localhost:5820/");
conn.setCredentials("admin", "admin");

conn.query({database: "sample",
  query: "select distinct * where { ?s ?p ?o }",
  limit: 10,
  offset: 0},
  function (data) {
  //console.log(data.results.bindings);
  for (i=0; i

View more ways to use stardog

Stardog.js

Universal Javascript fetch wrapper for communicating with the Stardog HTTP server.

What is it?

This framework wraps all the functionality of a client for the Stardog DBMS, and provides access to a full set of functions such as executing SPARQL queries, administrative tasks on Stardog, and the use of the Reasoning API.

All the implementation uses the HTTP protocol, since most of Stardog functionality is available using this protocol. For more information, go to the Stardog's HTTP Programming documentation.

This is a universal library and as such can be used in both the browser and Node.js.

Installation

To install stardog.js run:

npm install stardog

Usage

Stardog.js conforms to the Universal Module Definition API. To use it in Node.js, simply require or import it as you would any other Node module. To use it in the browser, you can either:

Do the same as you would with Node.js, in which case you'll have to use webpack, parcel, browserify, or some other module bundler,
Use require.js or some other module loader, or
Directly import the built stardog.js file in your HTML (e.g., ``) and then reference the global stardogjs object (e.g., stardogjs.query.execute(/* . . . */)).

Development

To get started, just clone the project. You'll need a local copy of Stardog to be able to run the tests. For more information on starting the Stardog DB service and how it works, go to Stardog's documentation, where you'll find everything you need to get up and running with Stardog.

Go to https://stardog.com, download and install the database and load the data provided in data/ using the script in the repository.

Start the Stardog server

stardog-admin server start

Install stardog.js dependencies:

npm install

Running Tests

In order to contribute changes, all test cases must pass. With the Stardog server running, execute the following command to run all test cases in test/spec:

npm test

To test the cluster commands you will need to first start a Stardog cluster then run the cluster suite. The easiest way to do this is to run docker-compose to start a cluster:

docker-compose -f .circleci/docker-compose.yml up

Then run the cluster test suite in test/cluster:

npm run test:cluster

Contributing

Fork, clone and develop, write or amend tests, and then open a PR. All PRs go against "master". This project uses prettier on file commit, so don't worry about style as it'll just get rewritten when you commit your changes.

Releasing

First, ensure that there is a milstone for the release version, and that all PRs that you want to appear in the CHANGELOG are tagged with that milestone. The milestone must be closed before publishing.

If you have publishing rights, BE SURE TO RUN npm version (major|minor|patch) IMMEDIATELY BEFORE PUBLISHING. This will ensure that the build is up-to-date and will also (1) bump the version number in package.json accordingly, (2) create a git tag matching the version number, and (3) automatically update the README and the CHANGELOG using our type declarations and data from the stardog.js GitHub repo. For this process to work correctly, you will need to have generated a GitHub OAuth token and assigned it to the MDCHANGELOG_TOKEN environment variable (the name of the token is a relic of the fact that this repo once used mdchangelog to generate changelogs; it now uses a custom script). You can then publish by running npm publish. In order to ensure that this process is followed, there will be a very annoying alert triggered whenever you publish; if you're all set, just ignore the alert.

After releasing, be sure to push to master, including the tags (so that the release is reflected on GitHub).

Version/Support Details

Each release of stardog.js is tested against the most recent version of Stardog available at the time of the release. The relationship between versions of stardog.js and versions of Stardog is detailed in the following table:

stardog.js Version	Supported Stardog Version(s)
6.x.x	10.x.x
5.x.x	9.x.x
4.x.x	8.x.x
3.x.x	7.x.x
2.x.x*	6.x.x
1.x.x*	5.x.x
0.x.x*	any version < 5

* = No longer supported

We support and maintain a particular version of stardog.js only if the corresponding Stardog version(s) is (are) officially supported and maintained. For example, we no longer support v0.x.x of stardog.js, as the corresponding Stardog versions are no longer supported. (That said, later versions of stardog.js will often mostly work with earlier Stardog versions. We just don't test this or make any guarantees to that effect.)

Quick Example

const { Connection, query } = require('stardog');

const conn = new Connection({
  username: 'admin',
  password: 'admin',
  endpoint: 'https://localhost:5820',
});

query
  .execute(
    conn,
    'myDatabaseName',
    'select distinct ?s where { ?s ?p ?o }',
    'application/sparql-results+json',
    {
      limit: 10,
      reasoning: true,
      offset: 0,
    }
  )
  .then(({ body }) =&gt; {
    console.log(body.results.bindings);
  });