← Home

@credo-ts/askar-to-drizzle-storage-migration

npm Repository Homepage

<p align="center"> <br /> <img alt="Credo Logo" src="https://github.com/openwallet-foundation/credo-ts/blob/c7886cb8377ceb8ee4efe8d264211e561a75072d/images/credo-logo.png" height="250px" /> </p> <h1 align="center"><b>Credo Askar to Drizz

5
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

openwalletfoundationtimoglastragenaris

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package now published via GitHub Actions CI/CD with SLSA attestation from the same openwallet-foundation org; legitimate automation transition. ai
maintainer-change maintainer-added AI (maintainer-change): genaris added as maintainer aligns with openwallet-foundation/credo-ts org; no malicious indicators. ai
dependencies unvetted-dep:@credo-ts/tenants AI (dependencies): Sibling package from the same credo-ts monorepo; unvetted status is a pipeline gap, not a risk. ai
dependencies unvetted-dep:@credo-ts/drizzle-storage AI (dependencies): Sibling package from the same credo-ts monorepo; unvetted status is a pipeline gap, not a risk. ai

Versions (showing 5 of 5)

Version Deps Published
0.7.0 4 / 2
0.6.3 4 / 2
0.6.2 4 / 2
0.6.1 4 / 2
0.6.0 4 / 2

v0.6.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.

v0.6.2

2 findings
HIGH Publisher changed: openwalletfoundation → GitHub Actions (on 2026-02-04) provenance

This version was published by a different npm account than previous versions on 2026-02-04. 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.

v0.6.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.

v0.6.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.