@docknetwork/credential-sdk
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@comunica/query-sparql-rdfjs | AI (phantom-deps): Used via config/dynamic loading, not a direct import. | ai | |
| dependencies | unvetted-dep:@comunica/actor-init-sparql-rdfjs | AI (dependencies): SPARQL/RDF engine used for JSON-LD/VC processing. | ai | |
| phantom-deps | phantom-dep:@comunica/actor-init-sparql-rdfjs | AI (phantom-deps): Referenced via config, not a direct import concern. | ai | |
| dependencies | unvetted-dep:elliptic | AI (dependencies): Widely used elliptic-curve lib, standard crypto dependency. | ai | |
| dependencies | unvetted-dep:@docknetwork/crypto-utils | AI (dependencies): First-party org package, part of same monorepo ecosystem. | ai | |
| dependencies | unvetted-dep:@sphereon/pex | AI (dependencies): Established SSI ecosystem dependency, long-standing usage. | ai | |
| dependencies | unvetted-dep:@transmute/json-web-signature | AI (dependencies): Established SSI ecosystem dependency, long-standing usage. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dock SDK publishes infrequently; 536-day gap is consistent with prior cadence for this org. | ai | |
| provenance | no-provenance | AI (provenance): Established docknetwork SDK; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:uuidv4 | AI (phantom-deps): uuidv4 is declared in package.json dependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.56.2 | 29 / 34 | |
| 0.56.1 | 29 / 34 | |
| 0.55.0 | 29 / 34 | |
| 0.54.19 | 29 / 34 | |
| 0.54.18 | 29 / 34 | |
| 0.54.17 | 29 / 34 | |
| 0.54.16 | 29 / 33 | |
| 0.54.11 | 27 / 33 | |
| 0.17.0 | 27 / 33 | |
| 0.9.0 | 27 / 33 | |
| 0.8.0 | 27 / 33 | |
| 0.7.0 | 27 / 33 | |
| 0.5.0 | 26 / 33 | |
| 0.4.0 | 26 / 33 |
v0.56.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.56.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.55.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.54.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.54.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.