@wppconnect/wa-version
List of WhatsApp Web HTML
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 100 of 2459)
| Version | Deps | Published |
|---|---|---|
| 1.5.2622 | 2 / 22 | |
| 1.5.2621 | 2 / 22 | |
| 1.5.2620 | 2 / 22 | |
| 1.5.2619 | 2 / 22 | |
| 1.5.2618 | 2 / 22 | |
| 1.5.2617 | 2 / 22 | |
| 1.5.2616 | 2 / 22 | |
| 1.5.2615 | 2 / 22 | |
| 1.5.2614 | 2 / 22 | |
| 1.5.2613 | 2 / 22 | |
| 1.5.2612 | 2 / 22 | |
| 1.5.2611 | 2 / 22 | |
| 1.5.2610 | 2 / 22 | |
| 1.5.2609 | 2 / 22 | |
| 1.5.2608 | 2 / 22 | |
| 1.5.2607 | 2 / 22 | |
| 1.5.2606 | 2 / 22 | |
| 1.5.2605 | 2 / 22 | |
| 1.5.2604 | 2 / 22 | |
| 1.5.2603 | 2 / 22 | |
| 1.5.2602 | 2 / 22 | |
| 1.5.2601 | 2 / 22 | |
| 1.5.2600 | 2 / 22 | |
| 1.5.2599 | 2 / 22 | |
| 1.5.2598 | 2 / 22 | |
| 1.5.2597 | 2 / 22 | |
| 1.5.2596 | 2 / 22 | |
| 1.5.2595 | 2 / 22 | |
| 1.5.2594 | 2 / 22 | |
| 1.5.2593 | 2 / 22 | |
| 1.5.2592 | 2 / 22 | |
| 1.5.2591 | 2 / 22 | |
| 1.5.2590 | 2 / 22 | |
| 1.5.2589 | 2 / 22 | |
| 1.5.2588 | 2 / 22 | |
| 1.5.2587 | 2 / 22 | |
| 1.5.2586 | 2 / 22 | |
| 1.5.2585 | 2 / 22 | |
| 1.5.2584 | 2 / 22 | |
| 1.5.2583 | 2 / 22 | |
| 1.5.2582 | 2 / 22 | |
| 1.5.2581 | 2 / 22 | |
| 1.5.2580 | 2 / 22 | |
| 1.5.2579 | 2 / 22 | |
| 1.5.2578 | 2 / 22 | |
| 1.5.2577 | 2 / 22 | |
| 1.5.2576 | 2 / 22 | |
| 1.5.2575 | 2 / 22 | |
| 1.5.2574 | 2 / 22 | |
| 1.5.2573 | 2 / 22 | |
| 1.5.2572 | 2 / 22 | |
| 1.5.2571 | 2 / 22 | |
| 1.5.2570 | 2 / 22 | |
| 1.5.2569 | 2 / 22 | |
| 1.5.2568 | 2 / 22 | |
| 1.5.2567 | 2 / 22 | |
| 1.5.2566 | 2 / 22 | |
| 1.5.2565 | 2 / 22 | |
| 1.5.2564 | 2 / 22 | |
| 1.5.2563 | 2 / 22 | |
| 1.5.2562 | 2 / 22 | |
| 1.5.2561 | 2 / 22 | |
| 1.5.2560 | 2 / 22 | |
| 1.5.2559 | 2 / 22 | |
| 1.5.2558 | 2 / 22 | |
| 1.5.2557 | 2 / 22 | |
| 1.5.2556 | 2 / 22 | |
| 1.5.2555 | 2 / 22 | |
| 1.5.2554 | 2 / 22 | |
| 1.5.2553 | 2 / 22 | |
| 1.5.2552 | 2 / 22 | |
| 1.5.2551 | 2 / 22 | |
| 1.5.2550 | 2 / 22 | |
| 1.5.2549 | 2 / 22 | |
| 1.5.2548 | 2 / 22 | |
| 1.5.2547 | 2 / 22 | |
| 1.5.2546 | 2 / 22 | |
| 1.5.2545 | 2 / 22 | |
| 1.5.2544 | 2 / 22 | |
| 1.5.2543 | 2 / 22 | |
| 1.5.2542 | 2 / 22 | |
| 1.5.2541 | 2 / 22 | |
| 1.5.2540 | 2 / 22 | |
| 1.5.2539 | 2 / 22 | |
| 1.5.2538 | 2 / 22 | |
| 1.5.2537 | 2 / 22 | |
| 1.5.2536 | 2 / 22 | |
| 1.5.2535 | 2 / 22 | |
| 1.5.2534 | 2 / 22 | |
| 1.5.2533 | 2 / 22 | |
| 1.5.2532 | 2 / 22 | |
| 1.5.2531 | 2 / 22 | |
| 1.5.2530 | 2 / 22 | |
| 1.5.2529 | 2 / 22 | |
| 1.5.2528 | 2 / 22 | |
| 1.5.2527 | 2 / 22 | |
| 1.5.2526 | 2 / 22 | |
| 1.5.2525 | 2 / 22 | |
| 1.5.2524 | 2 / 22 | |
| 1.5.2523 | 2 / 22 |
v1.5.2614
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2611
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2610
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2578
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2576
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2572
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2571
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2570
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2568
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2567
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2566
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2564
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2563
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2562
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2561
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2560
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2558
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2557
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2556
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2555
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2554
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2553
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2552
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2551
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2550
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2549
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2547
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2546
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2545
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2544
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2543
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2542
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2541
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2540
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2539
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2538
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2537
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2536
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2534
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2532
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2526
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2525
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2523
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.