← Home

n3

4
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rubenverborghrubensworks

Keywords

turtlerdfn3streamingasynchronous

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from rubensworks to GitHub Actions is a legitimate CI/CD automation move for the rdfjs/N3.js project, backed by SLSA provenance attestation. ai
publish-pattern dormant-publish AI (publish-pattern): Package has 139 versions and is actively maintained; dormancy signal is a measurement artifact. SLSA attestation confirms legitimate CI/CD publish. ai
typosquat typosquat.levenshtein:pg AI (typosquat): n3 is a 14-year-old legitimate RDF library (N3.js), not a typosquat of pg. Short name similarity is coincidental; packages serve entirely different purposes. ai
typosquat typosquat.levenshtein:qs AI (typosquat): n3 is a 14-year-old legitimate RDF library (N3.js), not a typosquat of qs. Short name similarity is coincidental; packages serve entirely different purposes. ai

Versions (showing 4 of 4)

Version Deps Published
2.0.3 2 / 18
2.0.2 2 / 18
2.0.1 2 / 18
2.0.0 2 / 18

v2.0.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.2

2 findings
HIGH Publisher changed: rubensworks → GitHub Actions (on 2026-03-07) provenance

This version was published by a different npm account than previous versions on 2026-03-07. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.