@dynamic-labs/waas-svm MIT 51 versions

@dynamic-labs/waas-svm

npm Homepage

A React SDK for implementing wallet web3 authentication and authorization to your website.

51

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

packaging-at-dynamic-labs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
bogus-package	bogus-package	AI (bogus-package): Dynamic Labs SDK packages consistently have minimal READMEs; not indicative of spam across this package family.	ai	2026/05/30
phantom-deps	phantom-dep:@dynamic-labs/types	AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via sibling packages.	ai	2026/05/30
provenance	publisher-changed	AI (provenance): Dynamic Labs transitioned to GitHub Actions CI publishing; consistent with org-wide automated release pipeline.	ai	2026/05/20
semgrep	semgrep:hex-decode	AI (semgrep): Buffer.from(signature, 'hex') is standard Solana transaction signature encoding; not obfuscation.	ai	2026/05/16
phantom-deps	phantom-dep:@dynamic-labs/rpc-providers	AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic unreliable for bundled packages.	ai	2026/05/16

Versions (showing 51 of 197)

View all versions

Version	Deps	Published
4.88.1	13 / 0	2026-06-04
4.88.0	13 / 0	2026-06-04
4.87.2	13 / 0	2026-06-03
4.87.1	13 / 0	2026-06-03
4.87.0	13 / 0	2026-06-02
4.86.0	13 / 0	2026-06-01
4.85.0	13 / 0	2026-05-29
4.84.1	13 / 0	2026-05-28
4.84.0	13 / 0	2026-05-22
4.83.1	13 / 0	2026-05-14
4.83.0	13 / 0	2026-05-11
4.82.0	13 / 0	2026-05-11
4.81.0	13 / 0	2026-05-08
4.80.0	13 / 0	2026-05-05
4.79.2	13 / 0	2026-05-04
4.79.1	13 / 0	2026-05-04
4.79.0	13 / 0	2026-04-30
4.78.1	13 / 0	2026-04-30
4.78.0	13 / 0	2026-04-22
4.77.4	13 / 0	2026-04-21
4.77.3	13 / 0	2026-04-18
4.77.2	13 / 0	2026-04-16
4.77.1	13 / 0	2026-04-10
4.77.0	13 / 0	2026-04-10
4.76.0	13 / 0	2026-04-06
4.75.0	13 / 0	2026-04-03
4.74.1	13 / 0	2026-04-03
4.74.0	13 / 0	2026-04-02
4.73.2	13 / 0	2026-03-31
4.73.0	13 / 0	2026-03-30
4.72.0	13 / 0	2026-03-26
4.71.0	13 / 0	2026-03-24
4.70.0	13 / 0	2026-03-23
4.69.0	13 / 0	2026-03-20
4.68.0	13 / 0	2026-03-19
4.67.2	13 / 0	2026-03-13
4.67.1	13 / 0	2026-03-10
4.67.0	13 / 0	2026-03-09
4.66.0	13 / 0	2026-03-02
4.65.0	13 / 0	2026-02-27
4.64.0	13 / 0	2026-02-25
4.63.1	13 / 0	2026-02-25
4.63.0	13 / 0	2026-02-24
4.62.0	13 / 0	2026-02-23
4.61.7	13 / 0	2026-02-20
4.61.6	13 / 0	2026-02-19
4.61.5	13 / 0	2026-02-19
4.61.4	13 / 0	2026-02-15
4.61.3	13 / 0	2026-02-13
4.61.2	13 / 0	2026-02-13
4.61.1	13 / 0	2026-02-11

v4.88.1

1 finding

LOW No provenance attestation provenance

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

v4.88.0

1 finding

LOW No provenance attestation provenance

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

v4.87.2

1 finding

LOW No provenance attestation provenance

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

v4.87.1

1 finding

LOW No provenance attestation provenance

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

v4.87.0

1 finding

LOW No provenance attestation provenance

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

v4.86.0

1 finding

LOW No provenance attestation provenance

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

v4.85.0

1 finding

LOW No provenance attestation provenance

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

v4.84.1

1 finding

LOW No provenance attestation provenance

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

v4.84.0

1 finding

LOW No provenance attestation provenance

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

v4.83.1

1 finding

LOW No provenance attestation provenance

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

v4.83.0

1 finding

LOW No provenance attestation provenance

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

v4.82.0

1 finding

LOW No provenance attestation provenance

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

v4.81.0

1 finding

LOW No provenance attestation provenance

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

v4.80.0

1 finding

LOW No provenance attestation provenance

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

v4.79.2

1 finding

LOW No provenance attestation provenance

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

v4.79.1

1 finding

LOW No provenance attestation provenance

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

v4.79.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.

v4.78.1

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-30) provenance

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

LOW No provenance attestation provenance

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

v4.78.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-22) provenance

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

LOW No provenance attestation provenance

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

v4.77.4

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-21) provenance

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

LOW No provenance attestation provenance

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

v4.77.3

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-18) provenance

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

LOW No provenance attestation provenance

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

v4.77.2

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-16) provenance

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

LOW No provenance attestation provenance

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

v4.77.1

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-10) provenance

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

LOW No provenance attestation provenance

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

v4.77.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-10) provenance

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

LOW No provenance attestation provenance

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

v4.76.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-06) provenance

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

LOW No provenance attestation provenance

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

v4.75.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-03) provenance

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

LOW No provenance attestation provenance

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

v4.74.1

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-03) provenance

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

LOW No provenance attestation provenance

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

v4.74.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-04-02) provenance

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

LOW No provenance attestation provenance

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

v4.73.2

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-31) provenance

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

LOW No provenance attestation provenance

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

v4.73.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-30) provenance

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

LOW No provenance attestation provenance

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

v4.72.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-26) provenance

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

LOW No provenance attestation provenance

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

v4.71.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-24) provenance

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

LOW No provenance attestation provenance

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

v4.70.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-23) provenance

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

LOW No provenance attestation provenance

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

v4.69.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-20) provenance

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

LOW No provenance attestation provenance

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

v4.68.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-19) provenance

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

LOW No provenance attestation provenance

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

v4.67.2

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-13) provenance

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

LOW No provenance attestation provenance

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

v4.67.1

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-10) provenance

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

LOW No provenance attestation provenance

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

v4.67.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-09) provenance

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

LOW No provenance attestation provenance

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

v4.66.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-03-02) provenance

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

LOW No provenance attestation provenance

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

v4.65.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-27) provenance

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

LOW No provenance attestation provenance

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

v4.64.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-25) provenance

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

LOW No provenance attestation provenance

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

v4.63.1

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-25) provenance

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

LOW No provenance attestation provenance

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

v4.63.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-24) provenance

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

LOW No provenance attestation provenance

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

v4.62.0

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-23) provenance

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

LOW No provenance attestation provenance

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

v4.61.7

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-20) provenance

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

LOW No provenance attestation provenance

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

v4.61.6

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-19) provenance

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

LOW No provenance attestation provenance

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

v4.61.5

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-19) provenance

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

LOW No provenance attestation provenance

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

v4.61.4

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-15) provenance

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

LOW No provenance attestation provenance

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

v4.61.3

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-13) provenance

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

LOW No provenance attestation provenance

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

v4.61.2

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-13) provenance

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

LOW No provenance attestation provenance

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

v4.61.1

2 findings

HIGH Publisher changed: packaging-at-dynamic-labs → GitHub Actions (on 2026-02-11) provenance

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

LOW No provenance attestation provenance

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