← Home

@reown/appkit-cli

npm Repository Homepage

Reown AppKit CLI

55
Versions
ISC
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

cyberdrkreown-npm-org

Keywords

appkitwalletonboardingreowndappsweb3wagmiethereumsolanabitcoin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:figlet AI (phantom-deps): figlet used via config reference, not a direct import; stable false positive. ai

Versions (showing 55 of 55)

Version Deps Published
1.8.23 3 / 6
1.8.22 3 / 6
1.8.21 3 / 6
1.8.20 3 / 6
1.8.19 3 / 6
1.8.18 3 / 6
1.8.17 3 / 6
1.8.16 3 / 6
1.8.15 3 / 6
1.8.14 3 / 6
1.8.13 3 / 6
1.8.12 3 / 6
1.8.11 3 / 6
1.8.10 3 / 6
1.8.9 3 / 6
1.8.8 3 / 6
1.8.7 3 / 6
1.8.5 3 / 6
1.8.4 3 / 6
1.8.3 4 / 6
1.8.2 4 / 6
1.8.1 4 / 6
1.8.0 4 / 6
1.7.20 4 / 6
1.7.19 4 / 6
1.7.18 4 / 6
1.7.17 4 / 6
1.7.16 4 / 6
1.7.15 4 / 6
1.7.14 4 / 6
1.7.13 4 / 6
1.7.12 4 / 6
1.7.11 4 / 6
1.7.10 4 / 6
1.7.9 4 / 6
1.7.8 4 / 6
1.7.7 4 / 6
1.7.6 4 / 6
1.7.5 4 / 6
1.7.4 4 / 6
1.7.3 4 / 6
1.7.2 4 / 6
1.7.1 4 / 6
1.7.0 4 / 6
1.6.9 4 / 6
1.6.8 4 / 6
1.6.7 4 / 6
1.6.6 4 / 6
1.6.5 4 / 6
1.6.4 4 / 6
1.6.3 4 / 6
1.6.2 4 / 6
1.6.1 4 / 6
1.6.0 4 / 6
1.5.3 4 / 6

v1.8.23

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.

v1.8.22

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.

v1.7.3

2 findings
MEDIUM Publisher changed: rocky-wc → reown-npm-org (on 2025-04-15, unremoved on npm for 458d) provenance

This version was published by a different npm account (reown-npm-org) than the most recent previously approved version (rocky-wc) on 2025-04-15. It has since remained available on npm for 458 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.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.

v1.5.3

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.