← Home

@reown/appkit-siwx

The chain agnostic tool to enable authentication for AppKit applications.

51
Versions
SEE LICENSE IN LICENSE.md
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
provenance no-provenance AI (provenance): Reown org publishes without Sigstore provenance consistently; stable false positive for this publisher. ai
phantom-deps phantom-dep:@reown/appkit-utils AI (phantom-deps): @reown/appkit-utils is a same-org sibling dep; phantom-dep false positive for monorepo packages. ai

Versions (showing 51 of 65)

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

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.

INFO No provenance attestation provenance

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

v1.7.2

1 finding
INFO No provenance attestation provenance

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

v1.7.1

1 finding
INFO No provenance attestation provenance

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

v1.7.0

1 finding
INFO No provenance attestation provenance

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

v1.6.9

1 finding
INFO No provenance attestation provenance

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

v1.6.8

1 finding
INFO No provenance attestation provenance

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

v1.6.7

1 finding
INFO No provenance attestation provenance

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

v1.6.6

1 finding
INFO No provenance attestation provenance

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

v1.6.5

1 finding
INFO No provenance attestation provenance

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

v1.6.4

1 finding
INFO No provenance attestation provenance

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