🚀 Socket Launch Week Day 5:Introducing Repository Access Permissions and Custom Roles.Learn more
Sign In

@mochi.js/cli

Package Overview
Dependencies
Maintainers
1
Versions
15
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@mochi.js/cli - npm Package Compare versions

Comparing version
0.2.9
to
0.2.10
+3
-3
package.json
{
"name": "@mochi.js/cli",
"version": "0.2.9",
"version": "0.2.10",
"description": "The mochi command — browsers install, capture, harness, work. The CLI surface for mochi.",

@@ -44,4 +44,4 @@ "license": "MIT",

"@mochi.js/consistency": "^0.1.4",
"@mochi.js/core": "^0.9.2",
"@mochi.js/harness": "^0.1.14"
"@mochi.js/core": "^0.9.3",
"@mochi.js/harness": "^0.1.15"
},

@@ -48,0 +48,0 @@ "publishConfig": {

@@ -51,4 +51,18 @@ /**

* 3. stable (no .0 minor — those are dev tip)
* 4. matches the major of the captured-baseline majority in
* `@mochi.js/profiles/data/<id>/profile.json`. Drift between this
* pin and the captured-profile UA is the canonical R-004
* mismatch — detectors fingerprint UA-vs-binary divergence as
* "Different browser version".
*
* 2026-05-10: rolled back from 148.0.7778.97 → 147.0.7727.138. The
* captured-profile catalog is still on Chrome 146/147; pinning 148
* shipped a 1-major UA-vs-binary mismatch on every install. The
* three most-used captures (linux-chrome-stable, mac-m4-chrome-stable,
* mac-chrome-beta) now match this pin byte-exactly. The three older
* 146 captures (mac-chrome-stable, windows-chrome-stable,
* mac-brave-stable) still mismatch by 1 minor — tracked for the
* next recapture pass.
*/
export const PINNED_FALLBACK_VERSION = "148.0.7778.97" as const;
export const PINNED_FALLBACK_VERSION = "147.0.7727.138" as const;
export const PINNED_FALLBACK_CHANNEL: Channel = "stable";

@@ -55,0 +69,0 @@

@@ -9,3 +9,3 @@ /**

*/
export const VERSION = "0.2.8" as const;
export const VERSION = "0.2.9" as const;

@@ -12,0 +12,0 @@ /**