open-agreements 0.7.6 → 0.7.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +1 -1
- package/content/templates/openagreements-due-diligence-request-list/template.docx +0 -0
- package/content/templates/openagreements-due-diligence-request-list/template.md +1 -1
- package/dist/core/fill-pipeline.d.ts.map +1 -1
- package/dist/core/fill-pipeline.js +0 -8
- package/dist/core/fill-pipeline.js.map +1 -1
- package/dist/core/unified-pipeline.d.ts.map +1 -1
- package/dist/core/unified-pipeline.js +4 -6
- package/dist/core/unified-pipeline.js.map +1 -1
- package/gemini-extension.json +1 -1
- package/node_modules/@xmldom/xmldom/CHANGELOG.md +939 -0
- package/node_modules/@xmldom/xmldom/LICENSE +8 -0
- package/node_modules/@xmldom/xmldom/SECURITY.md +50 -0
- package/node_modules/@xmldom/xmldom/index.d.ts +1664 -0
- package/node_modules/@xmldom/xmldom/lib/.eslintrc.yml +3 -0
- package/node_modules/@xmldom/xmldom/lib/conventions.js +429 -0
- package/node_modules/@xmldom/xmldom/lib/dom-parser.js +586 -0
- package/node_modules/@xmldom/xmldom/lib/dom.js +3192 -0
- package/node_modules/@xmldom/xmldom/lib/entities.js +2171 -0
- package/node_modules/@xmldom/xmldom/lib/errors.js +202 -0
- package/node_modules/@xmldom/xmldom/lib/grammar.js +533 -0
- package/node_modules/@xmldom/xmldom/lib/index.js +41 -0
- package/node_modules/@xmldom/xmldom/lib/sax.js +929 -0
- package/node_modules/@xmldom/xmldom/package.json +74 -0
- package/node_modules/@xmldom/xmldom/readme.md +364 -0
- package/node_modules/core-util-is/LICENSE +19 -0
- package/node_modules/core-util-is/README.md +3 -0
- package/node_modules/core-util-is/lib/util.js +107 -0
- package/node_modules/core-util-is/package.json +38 -0
- package/node_modules/immediate/LICENSE.txt +20 -0
- package/node_modules/immediate/README.md +93 -0
- package/node_modules/immediate/dist/immediate.js +75 -0
- package/node_modules/immediate/dist/immediate.min.js +1 -0
- package/node_modules/immediate/lib/browser.js +69 -0
- package/node_modules/immediate/lib/index.js +73 -0
- package/node_modules/immediate/package.json +42 -0
- package/node_modules/inherits/LICENSE +16 -0
- package/node_modules/inherits/README.md +42 -0
- package/node_modules/inherits/inherits.js +9 -0
- package/node_modules/inherits/inherits_browser.js +27 -0
- package/node_modules/inherits/package.json +29 -0
- package/node_modules/isarray/.npmignore +1 -0
- package/node_modules/isarray/.travis.yml +4 -0
- package/node_modules/isarray/Makefile +6 -0
- package/node_modules/isarray/README.md +60 -0
- package/node_modules/isarray/component.json +19 -0
- package/node_modules/isarray/index.js +5 -0
- package/node_modules/isarray/package.json +45 -0
- package/node_modules/isarray/test.js +20 -0
- package/node_modules/jszip/.codeclimate.yml +16 -0
- package/node_modules/jszip/.editorconfig +8 -0
- package/node_modules/jszip/.eslintrc.js +43 -0
- package/node_modules/jszip/.github/workflows/pr.yaml +58 -0
- package/node_modules/jszip/.jekyll-metadata +0 -0
- package/node_modules/jszip/.travis.yml +17 -0
- package/node_modules/jszip/CHANGES.md +204 -0
- package/node_modules/jszip/LICENSE.markdown +651 -0
- package/node_modules/jszip/README.markdown +33 -0
- package/node_modules/jszip/deps.js +37 -0
- package/node_modules/jszip/dist/jszip.js +11577 -0
- package/node_modules/jszip/dist/jszip.min.js +13 -0
- package/node_modules/jszip/graph.svg +601 -0
- package/node_modules/jszip/index.d.ts +330 -0
- package/node_modules/jszip/lib/base64.js +106 -0
- package/node_modules/jszip/lib/compressedObject.js +74 -0
- package/node_modules/jszip/lib/compressions.js +14 -0
- package/node_modules/jszip/lib/crc32.js +77 -0
- package/node_modules/jszip/lib/defaults.js +11 -0
- package/node_modules/jszip/lib/external.js +18 -0
- package/node_modules/jszip/lib/flate.js +85 -0
- package/node_modules/jszip/lib/generate/ZipFileWorker.js +539 -0
- package/node_modules/jszip/lib/generate/index.js +57 -0
- package/node_modules/jszip/lib/index.js +55 -0
- package/node_modules/jszip/lib/license_header.js +11 -0
- package/node_modules/jszip/lib/load.js +88 -0
- package/node_modules/jszip/lib/nodejs/NodejsStreamInputAdapter.js +74 -0
- package/node_modules/jszip/lib/nodejs/NodejsStreamOutputAdapter.js +42 -0
- package/node_modules/jszip/lib/nodejsUtils.js +57 -0
- package/node_modules/jszip/lib/object.js +384 -0
- package/node_modules/jszip/lib/readable-stream-browser.js +10 -0
- package/node_modules/jszip/lib/reader/ArrayReader.js +57 -0
- package/node_modules/jszip/lib/reader/DataReader.js +116 -0
- package/node_modules/jszip/lib/reader/NodeBufferReader.js +19 -0
- package/node_modules/jszip/lib/reader/StringReader.js +38 -0
- package/node_modules/jszip/lib/reader/Uint8ArrayReader.js +22 -0
- package/node_modules/jszip/lib/reader/readerFor.js +28 -0
- package/node_modules/jszip/lib/signature.js +7 -0
- package/node_modules/jszip/lib/stream/ConvertWorker.js +26 -0
- package/node_modules/jszip/lib/stream/Crc32Probe.js +24 -0
- package/node_modules/jszip/lib/stream/DataLengthProbe.js +29 -0
- package/node_modules/jszip/lib/stream/DataWorker.js +116 -0
- package/node_modules/jszip/lib/stream/GenericWorker.js +263 -0
- package/node_modules/jszip/lib/stream/StreamHelper.js +214 -0
- package/node_modules/jszip/lib/support.js +38 -0
- package/node_modules/jszip/lib/utf8.js +275 -0
- package/node_modules/jszip/lib/utils.js +501 -0
- package/node_modules/jszip/lib/zipEntries.js +261 -0
- package/node_modules/jszip/lib/zipEntry.js +293 -0
- package/node_modules/jszip/lib/zipObject.js +133 -0
- package/node_modules/jszip/package.json +67 -0
- package/node_modules/jszip/sponsors.md +21 -0
- package/node_modules/jszip/tsconfig.json +101 -0
- package/node_modules/jszip/vendor/FileSaver.js +247 -0
- package/node_modules/lie/README.md +62 -0
- package/node_modules/lie/dist/lie.js +350 -0
- package/node_modules/lie/dist/lie.min.js +1 -0
- package/node_modules/lie/dist/lie.polyfill.js +358 -0
- package/node_modules/lie/dist/lie.polyfill.min.js +1 -0
- package/node_modules/lie/lib/browser.js +273 -0
- package/node_modules/lie/lib/index.js +298 -0
- package/node_modules/lie/license.md +7 -0
- package/node_modules/lie/lie.d.ts +244 -0
- package/node_modules/lie/package.json +69 -0
- package/node_modules/lie/polyfill.js +4 -0
- package/node_modules/pako/LICENSE +21 -0
- package/node_modules/pako/README.md +191 -0
- package/node_modules/pako/dist/pako.js +6818 -0
- package/node_modules/pako/dist/pako.min.js +1 -0
- package/node_modules/pako/dist/pako_deflate.js +3997 -0
- package/node_modules/pako/dist/pako_deflate.min.js +1 -0
- package/node_modules/pako/dist/pako_inflate.js +3300 -0
- package/node_modules/pako/dist/pako_inflate.min.js +1 -0
- package/node_modules/pako/index.js +14 -0
- package/node_modules/pako/lib/deflate.js +400 -0
- package/node_modules/pako/lib/inflate.js +423 -0
- package/node_modules/pako/lib/utils/common.js +105 -0
- package/node_modules/pako/lib/utils/strings.js +187 -0
- package/node_modules/pako/lib/zlib/README +59 -0
- package/node_modules/pako/lib/zlib/adler32.js +51 -0
- package/node_modules/pako/lib/zlib/constants.js +68 -0
- package/node_modules/pako/lib/zlib/crc32.js +59 -0
- package/node_modules/pako/lib/zlib/deflate.js +1874 -0
- package/node_modules/pako/lib/zlib/gzheader.js +58 -0
- package/node_modules/pako/lib/zlib/inffast.js +345 -0
- package/node_modules/pako/lib/zlib/inflate.js +1556 -0
- package/node_modules/pako/lib/zlib/inftrees.js +343 -0
- package/node_modules/pako/lib/zlib/messages.js +32 -0
- package/node_modules/pako/lib/zlib/trees.js +1222 -0
- package/node_modules/pako/lib/zlib/zstream.js +47 -0
- package/node_modules/pako/package.json +44 -0
- package/node_modules/process-nextick-args/index.js +45 -0
- package/node_modules/process-nextick-args/license.md +19 -0
- package/node_modules/process-nextick-args/package.json +25 -0
- package/node_modules/process-nextick-args/readme.md +18 -0
- package/node_modules/readable-stream/.travis.yml +34 -0
- package/node_modules/readable-stream/CONTRIBUTING.md +38 -0
- package/node_modules/readable-stream/GOVERNANCE.md +136 -0
- package/node_modules/readable-stream/LICENSE +47 -0
- package/node_modules/readable-stream/README.md +58 -0
- package/node_modules/readable-stream/doc/wg-meetings/2015-01-30.md +60 -0
- package/node_modules/readable-stream/duplex-browser.js +1 -0
- package/node_modules/readable-stream/duplex.js +1 -0
- package/node_modules/readable-stream/lib/_stream_duplex.js +131 -0
- package/node_modules/readable-stream/lib/_stream_passthrough.js +47 -0
- package/node_modules/readable-stream/lib/_stream_readable.js +1019 -0
- package/node_modules/readable-stream/lib/_stream_transform.js +214 -0
- package/node_modules/readable-stream/lib/_stream_writable.js +685 -0
- package/node_modules/readable-stream/lib/internal/streams/BufferList.js +78 -0
- package/node_modules/readable-stream/lib/internal/streams/destroy.js +84 -0
- package/node_modules/readable-stream/lib/internal/streams/stream-browser.js +1 -0
- package/node_modules/readable-stream/lib/internal/streams/stream.js +1 -0
- package/node_modules/readable-stream/package.json +52 -0
- package/node_modules/readable-stream/passthrough.js +1 -0
- package/node_modules/readable-stream/readable-browser.js +7 -0
- package/node_modules/readable-stream/readable.js +19 -0
- package/node_modules/readable-stream/transform.js +1 -0
- package/node_modules/readable-stream/writable-browser.js +1 -0
- package/node_modules/readable-stream/writable.js +8 -0
- package/node_modules/safe-buffer/LICENSE +21 -0
- package/node_modules/safe-buffer/README.md +584 -0
- package/node_modules/safe-buffer/index.d.ts +187 -0
- package/node_modules/safe-buffer/index.js +62 -0
- package/node_modules/safe-buffer/package.json +37 -0
- package/node_modules/setimmediate/LICENSE.txt +20 -0
- package/node_modules/setimmediate/package.json +30 -0
- package/node_modules/setimmediate/setImmediate.js +186 -0
- package/node_modules/string_decoder/.travis.yml +50 -0
- package/node_modules/string_decoder/LICENSE +48 -0
- package/node_modules/string_decoder/README.md +47 -0
- package/node_modules/string_decoder/lib/string_decoder.js +296 -0
- package/node_modules/string_decoder/package.json +31 -0
- package/node_modules/util-deprecate/History.md +16 -0
- package/node_modules/util-deprecate/LICENSE +24 -0
- package/node_modules/util-deprecate/README.md +53 -0
- package/node_modules/util-deprecate/browser.js +67 -0
- package/node_modules/util-deprecate/node.js +6 -0
- package/node_modules/util-deprecate/package.json +27 -0
- package/package.json +1 -1
- package/skills/client-email/SKILL.md +8 -6
- package/skills/employment-contract/SKILL.md +23 -6
- package/skills/non-compete-contract-explainer/content/alabama.md +251 -0
- package/skills/non-compete-contract-explainer/content/alaska.md +160 -0
- package/skills/non-compete-contract-explainer/content/american-samoa.md +187 -0
- package/skills/non-compete-contract-explainer/content/arizona.md +293 -0
- package/skills/non-compete-contract-explainer/content/arkansas.md +235 -0
- package/skills/non-compete-contract-explainer/content/california.md +270 -0
- package/skills/non-compete-contract-explainer/content/cnmi.md +168 -0
- package/skills/non-compete-contract-explainer/content/colorado.md +277 -0
- package/skills/non-compete-contract-explainer/content/connecticut.md +220 -0
- package/skills/non-compete-contract-explainer/content/delaware.md +222 -0
- package/skills/non-compete-contract-explainer/content/district-of-columbia.md +263 -0
- package/skills/non-compete-contract-explainer/content/florida.md +267 -0
- package/skills/non-compete-contract-explainer/content/georgia.md +323 -0
- package/skills/non-compete-contract-explainer/content/guam.md +180 -0
- package/skills/non-compete-contract-explainer/content/hawaii.md +236 -0
- package/skills/non-compete-contract-explainer/content/idaho.md +258 -0
- package/skills/non-compete-contract-explainer/content/illinois.md +266 -0
- package/skills/non-compete-contract-explainer/content/india.md +269 -0
- package/skills/non-compete-contract-explainer/content/indiana.md +253 -0
- package/skills/non-compete-contract-explainer/content/iowa.md +232 -0
- package/skills/non-compete-contract-explainer/content/kansas.md +227 -0
- package/skills/non-compete-contract-explainer/content/kentucky.md +201 -0
- package/skills/non-compete-contract-explainer/content/louisiana.md +272 -0
- package/skills/non-compete-contract-explainer/content/maine.md +178 -0
- package/skills/non-compete-contract-explainer/content/maryland.md +244 -0
- package/skills/non-compete-contract-explainer/content/massachusetts.md +272 -0
- package/skills/non-compete-contract-explainer/content/michigan.md +222 -0
- package/skills/non-compete-contract-explainer/content/minnesota.md +171 -0
- package/skills/non-compete-contract-explainer/content/mississippi.md +237 -0
- package/skills/non-compete-contract-explainer/content/missouri.md +219 -0
- package/skills/non-compete-contract-explainer/content/montana.md +202 -0
- package/skills/non-compete-contract-explainer/content/nebraska.md +206 -0
- package/skills/non-compete-contract-explainer/content/nevada.md +278 -0
- package/skills/non-compete-contract-explainer/content/new-hampshire.md +233 -0
- package/skills/non-compete-contract-explainer/content/new-jersey.md +277 -0
- package/skills/non-compete-contract-explainer/content/new-mexico.md +244 -0
- package/skills/non-compete-contract-explainer/content/new-york.md +226 -0
- package/skills/non-compete-contract-explainer/content/north-carolina.md +346 -0
- package/skills/non-compete-contract-explainer/content/north-dakota.md +187 -0
- package/skills/non-compete-contract-explainer/content/ohio.md +207 -0
- package/skills/non-compete-contract-explainer/content/oklahoma.md +196 -0
- package/skills/non-compete-contract-explainer/content/oregon.md +359 -0
- package/skills/non-compete-contract-explainer/content/pennsylvania.md +254 -0
- package/skills/non-compete-contract-explainer/content/philippines.md +211 -0
- package/skills/non-compete-contract-explainer/content/puerto-rico.md +163 -0
- package/skills/non-compete-contract-explainer/content/rhode-island.md +171 -0
- package/skills/non-compete-contract-explainer/content/singapore.md +229 -0
- package/skills/non-compete-contract-explainer/content/south-carolina.md +226 -0
- package/skills/non-compete-contract-explainer/content/south-dakota.md +222 -0
- package/skills/non-compete-contract-explainer/content/tennessee.md +251 -0
- package/skills/non-compete-contract-explainer/content/texas.md +297 -0
- package/skills/non-compete-contract-explainer/content/us-virgin-islands.md +193 -0
- package/skills/non-compete-contract-explainer/content/utah.md +250 -0
- package/skills/non-compete-contract-explainer/content/vermont.md +193 -0
- package/skills/non-compete-contract-explainer/content/virginia.md +213 -0
- package/skills/non-compete-contract-explainer/content/washington.md +296 -0
- package/skills/non-compete-contract-explainer/content/west-virginia.md +187 -0
- package/skills/non-compete-contract-explainer/content/wisconsin.md +293 -0
- package/skills/non-compete-contract-explainer/content/wyoming.md +55 -45
- package/skills/non-compete-contract-explainer/manifest.json +523 -1
|
@@ -44,42 +44,44 @@ The statute covers covenants that restrict the right of any person to receive co
|
|
|
44
44
|
|
|
45
45
|
The practical reading is that a standard post-employment employee non-compete should not be reused in Wyoming after the effective date unless it is deliberately drafted into one of the remaining statutory categories.
|
|
46
46
|
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
**Short answer.** Likely yes under the dominant 2025 law-firm commentary, but that is still an interpretation rather than a Wyoming appellate holding.
|
|
50
|
-
|
|
51
|
-
The reason is the statutory phrase "any person"[^wyo-1-23-any-person]. State-specific law-firm commentary reads that wording broadly enough to reach independent contractors, not only W-2 employees [^littler-any-status][^faegre-includes-contractors][^fisher-colorado-any-person]. That same broad phrasing closely mirrors Colorado's void-for-compensation rule, which is why commentary points to Colorado as the analogue. *See our companion note on [whether Colorado employee non-competes are enforceable](/legal/non-compete/colorado#enforceability).*
|
|
52
|
-
|
|
53
|
-
That is a strong drafting assumption for Wyoming templates, but a careful note should still say that Wyoming courts have not yet issued a controlling appellate decision on the contractor question.
|
|
47
|
+
The statute does not erase every Wyoming non-compete. Two categories fall outside the void and remain governed by Wyoming common law and its demanding reasonableness baseline: agreements entered into before July 1, 2025, which the act does not alter[^sf107-prospective-savings], and non-compete covenants drafted to fit a statutory exception. Fitting an exception keeps a non-compete out of the statutory void but does not make it automatically enforceable — such a covenant must still satisfy the common-law reasonableness elements[^malave-reasonableness-baseline], and Wyoming courts strictly construe[^brown-strict-construction-baseline] restraints against the employer. The next question covers what law still governs those covenants; the pre-2025 cohort also shrinks as those agreements age out.
|
|
54
48
|
|
|
55
|
-
## What law governs Wyoming non-compete
|
|
49
|
+
## What law governs Wyoming non-compete covenants the 2025 statute does not void? {#pre-2025-agreements}
|
|
56
50
|
|
|
57
|
-
**Short answer.**
|
|
51
|
+
**Short answer.** Wyoming common law governs them, applying the same demanding reasonableness baseline that predated the statute. Two cohorts fall outside the statutory void: agreements entered into before July 1, 2025, which the act does not alter[^sf107-savings-clause], and non-compete covenants that fit a statutory exception.
|
|
58
52
|
|
|
59
|
-
|
|
53
|
+
Falling outside the statutory void does not make either cohort easy to enforce. Wyoming common law uses traditional enforceability elements[^malave-five-elements]: the covenant must be written, part of an employment contract, supported by reasonable consideration, reasonable in duration and geography, and not against public policy.
|
|
60
54
|
|
|
61
|
-
Wyoming cases also strictly construe non-competes[^brown-strict-construction] and put the burden on the employer to prove special circumstances that make the restraint reasonably necessary. For a post-hire covenant, continued employment alone is not enough consideration[^brown-separate-consideration].
|
|
55
|
+
Wyoming cases also strictly construe non-competes[^brown-strict-construction] and put the burden on the employer to prove special circumstances that make the restraint reasonably necessary. For a post-hire covenant, continued employment alone is not enough consideration[^brown-separate-consideration]. The pre-2025 cohort shrinks as those agreements age out. Among the statutory exceptions, the ones that operate as non-competes — such as the executive-and-management carve-out — remain subject to this same reasonableness analysis, while the capped repayment carve-out is an expense-recovery mechanism judged on the statutory schedule rather than the reasonableness test. A later question covers the four exceptions in detail, and a separate question covers whether a court will narrow an overbroad covenant.
|
|
62
56
|
|
|
63
57
|
> [!CAUTION]
|
|
64
58
|
> **Drafting note.**
|
|
65
59
|
>
|
|
66
60
|
> No published Wyoming authority addresses tolling a non-compete during a breach. Wyoming strictly construes restrictive covenants and puts the burden on the employer to justify the restraint [^brown-strict-construction]. A tolling provision adds duration that faces the same reasonableness scrutiny as the original term — without judicial willingness to trim — so the realistic downside is voiding the covenant, not narrowing it.
|
|
67
61
|
|
|
68
|
-
##
|
|
62
|
+
## Does Wyoming's non-compete ban apply to independent contractors? {#independent-contractors}
|
|
63
|
+
|
|
64
|
+
**Short answer.** Likely yes under the dominant 2025 law-firm commentary, but that is still an interpretation rather than a Wyoming appellate holding.
|
|
65
|
+
|
|
66
|
+
The reason is the statutory phrase "any person"[^wyo-1-23-any-person]. State-specific law-firm commentary reads that wording broadly enough to reach independent contractors, not only W-2 employees [^littler-any-status][^faegre-includes-contractors][^fisher-colorado-any-person]. That same broad phrasing closely mirrors Colorado's void-for-compensation rule, which is why commentary points to Colorado as the analogue. *See our companion note on [whether Colorado employee non-competes are enforceable](/legal/non-compete/colorado#enforceability).*
|
|
67
|
+
|
|
68
|
+
That is a strong drafting assumption for Wyoming templates, but a careful note should still say that Wyoming courts have not yet issued a controlling appellate decision on the contractor question.
|
|
69
|
+
|
|
70
|
+
## Can a Wyoming court narrow an overbroad non-compete? {#court-narrowing}
|
|
69
71
|
|
|
70
|
-
**Short answer.** No. The Wyoming Supreme Court
|
|
72
|
+
**Short answer.** No. The Wyoming Supreme Court will not rewrite an overbroad covenant[^hassler-no-blue-pencil] to bring it within the bounds of reason.
|
|
71
73
|
|
|
72
74
|
The court held that the entire agreement was void because the duration and geographic terms were unreasonable. That makes overbreadth more expensive in Wyoming than in states where courts may trim an unreasonable covenant down to an enforceable scope.
|
|
73
75
|
|
|
74
76
|
> [!CAUTION]
|
|
75
77
|
> **Drafting note.**
|
|
76
78
|
>
|
|
77
|
-
>
|
|
79
|
+
> A Wyoming court is unlikely to rescue an overbroad covenant by narrowing it later. That risk applies both to legacy agreements and to new agreements drafted inside a statutory exception [^holland-blue-pencil-warning].
|
|
78
80
|
|
|
79
81
|
> [!CAUTION]
|
|
80
82
|
> **Drafting note.**
|
|
81
83
|
>
|
|
82
|
-
>
|
|
84
|
+
> Where a covenant falls within a statutory exception and enforceability matters, enforceability is more likely when duration and geography are tied to specific business needs and the reasonableness analysis is documented at drafting time. Because a Wyoming court will void an overbroad covenant whole rather than trim it [^hassler-no-blue-pencil], the upside of an aggressive scope is small relative to the risk of losing the covenant entirely.
|
|
83
85
|
|
|
84
86
|
## What non-compete restrictions are still allowed in Wyoming after July 1, 2025? {#available-restrictions}
|
|
85
87
|
|
|
@@ -87,6 +89,8 @@ The court held that the entire agreement was void because the duration and geogr
|
|
|
87
89
|
|
|
88
90
|
The four statutory carveouts[^wyo-1-23-four-carveouts] are listed in Wyo. Stat. § 1-23-108(a). The repayment carveout is not a blank check; it is capped by the employee's tenure, with lower recovery percentages as service length increases.
|
|
89
91
|
|
|
92
|
+
Fitting one of these categories keeps a covenant out of the statutory void, but it does not make the covenant automatically enforceable — an exception covenant that operates as a non-compete is still judged under the common-law reasonableness baseline covered in the earlier question on what law governs covenants the statute does not void.
|
|
93
|
+
|
|
90
94
|
> [!CAUTION]
|
|
91
95
|
> **Drafting note.**
|
|
92
96
|
>
|
|
@@ -95,7 +99,7 @@ The four statutory carveouts[^wyo-1-23-four-carveouts] are listed in Wyo. Stat.
|
|
|
95
99
|
> [!CAUTION]
|
|
96
100
|
> **Drafting note.**
|
|
97
101
|
>
|
|
98
|
-
> The trade-secret exception covers covenants only to the extent they protect information that meets Wyoming's statutory trade-secret definition.
|
|
102
|
+
> The trade-secret exception covers covenants only to the extent they protect information that meets Wyoming's statutory trade-secret definition. Enforceability is more likely when the contractual definition of protected information is tied to that statutory bar and each category is documented as meeting it, since how broadly Wyoming courts read the carveout remains an open question [^littler-trade-secret-unsettled].
|
|
99
103
|
|
|
100
104
|
## Are customer non-solicitation agreements enforceable in Wyoming? {#customer-nonsolicits}
|
|
101
105
|
|
|
@@ -106,7 +110,7 @@ Brownstein takes the employer-friendly view that customer non-solicitation coven
|
|
|
106
110
|
> [!CAUTION]
|
|
107
111
|
> **Drafting note.**
|
|
108
112
|
>
|
|
109
|
-
>
|
|
113
|
+
> A narrow customer-relationship restriction carries less risk than language that prevents the person from earning compensation in a field, territory, or role. The closer the clause gets to a work ban, the more non-compete risk it carries [^fisher-classification-question].
|
|
110
114
|
|
|
111
115
|
## Are employee non-solicitation agreements enforceable in Wyoming? {#employee-nonsolicits}
|
|
112
116
|
|
|
@@ -125,15 +129,15 @@ Brownstein says the statute does not affect nondisclosure or confidentiality agr
|
|
|
125
129
|
> [!CAUTION]
|
|
126
130
|
> **Drafting note.**
|
|
127
131
|
>
|
|
128
|
-
>
|
|
132
|
+
> A confidentiality clause that protects confidential information carries less risk than one drafted to prevent someone from working in a role, industry, or geography. The broader the definition of protected information, the more the clause begins to look like a non-compete substitute [^fisher-nda-question].
|
|
129
133
|
|
|
130
|
-
##
|
|
134
|
+
## Can Wyoming employers bind executives or managers to non-competes under the statutory exception? {#executives-managers}
|
|
131
135
|
|
|
132
|
-
**Short answer.**
|
|
136
|
+
**Short answer.** Possibly, but the exception is not self-defining. Wyoming allows covenants with executive and management personnel and their professional staff, but the statute does not define those terms.
|
|
133
137
|
|
|
134
|
-
The
|
|
138
|
+
The statutory exception covers executive and management personnel[^wyo-1-23-exec-staff]. Law-firm commentary flags the drafting gap [^faegre-exec-undefined], and other law-firm commentary points to Colorado cases as possible nonbinding guidance because Colorado once used similar language [^fisher-actual-duties][^holland-colorado-analogy].
|
|
135
139
|
|
|
136
|
-
|
|
140
|
+
Those comparisons point toward function over title: supervision, autonomy, hiring or firing authority, and a meaningful role in implementing management functions. A *manager* label alone is not the safest basis for the Wyoming exception.
|
|
137
141
|
|
|
138
142
|
## Can a Wyoming non-compete prevent a physician from practicing medicine? {#physicians}
|
|
139
143
|
|
|
@@ -146,15 +150,15 @@ The harder question is the phrase "between physicians"[^wyo-1-23-between-physici
|
|
|
146
150
|
> [!CAUTION]
|
|
147
151
|
> **Drafting note.**
|
|
148
152
|
>
|
|
149
|
-
> Wyoming voids physician-to-physician practice restraints and protects the departing physician's right to share continuing-practice information with rare-disorder patients [^wyo-1-23-physician-bc].
|
|
153
|
+
> Wyoming voids physician-to-physician practice restraints and protects the departing physician's right to share continuing-practice information with rare-disorder patients [^wyo-1-23-physician-bc]. Mirroring that statutory protection in the clause itself reduces risk, and relying on the broader exec/management exception for physicians employed by non-physician entities is riskier — the "between physicians"[^wyo-1-23-between-physicians] language leaves that scope unsettled [^holland-between-physicians].
|
|
150
154
|
|
|
151
|
-
##
|
|
155
|
+
## Are anti-moonlighting clauses risky under Wyoming's non-compete law? {#anti-moonlighting}
|
|
152
156
|
|
|
153
|
-
**Short answer.**
|
|
157
|
+
**Short answer.** Potentially. A narrow conflict-of-interest rule is different from a broad ban on outside work, but the statutory text creates risk for clauses that restrict compensation for labor.
|
|
154
158
|
|
|
155
|
-
The
|
|
159
|
+
The statute focuses on covenants that restrict compensation for skilled or unskilled labor [^wyo-1-23-compensation-focus]. Fisher Phillips specifically flags anti-moonlighting provisions as one of the adjacent covenant types Wyoming courts may need to classify under the 2025 statute [^fisher-anti-moonlighting].
|
|
156
160
|
|
|
157
|
-
|
|
161
|
+
This is useful to keep separate from non-competes because many employers do not call those clauses *non-competes*, even when they restrict outside work in a way that starts to resemble one.
|
|
158
162
|
|
|
159
163
|
## Can Wyoming employers recover relocation, education, or training expenses from departing employees? {#repayment-clauses}
|
|
160
164
|
|
|
@@ -165,13 +169,13 @@ Wyoming permits recovery of up to 100% of relocation, education, and training ex
|
|
|
165
169
|
> [!CAUTION]
|
|
166
170
|
> **Drafting note.**
|
|
167
171
|
>
|
|
168
|
-
>
|
|
172
|
+
> A clause drafted as an expense-recovery provision carries less risk than one that operates as a disguised penalty for competition. Enforceability is more likely when the amount is tied to actual relocation, education, or training expense and the statutory percentages [^ogletree-repayment-tier][^faegre-repayment-tier].
|
|
169
173
|
|
|
170
|
-
##
|
|
174
|
+
## Should employers update or re-review Wyoming restrictive covenant templates after July 1, 2025? {#template-updates}
|
|
171
175
|
|
|
172
|
-
**Short answer.**
|
|
176
|
+
**Short answer.** Probably yes — and at least re-review. Any form that contains a non-compete outside a statutory exception should be updated, while a form with no non-compete may already conform; either way the new statute turns unreviewed template rollover into a legal risk point, especially where an older covenant might have remained enforceable under common law.
|
|
173
177
|
|
|
174
|
-
Wyoming-specific commentary treats SF 107 as a major narrowing of employer practice, not a minor drafting tweak [^ogletree-review-revise].
|
|
178
|
+
Wyoming-specific commentary treats SF 107 as a major narrowing of employer practice, not a minor drafting tweak [^ogletree-review-revise]. A complete re-review usually covers non-compete templates, offer letters, incentive agreements, physician agreements, non-solicits, NDAs, anti-moonlighting clauses, and repayment provisions together.
|
|
175
179
|
|
|
176
180
|
Commentary specifically warns employers to evaluate routine replacement or updating programs because a new agreement after July 1, 2025 may replace something that was enforceable with something void [^littler-rollover-warning]. Where a grandfathered covenant needs changes, commentary suggests amending or renewing it rather than signing a fresh agreement, when the existing terms allow that, so the covenant is not treated as newly entered into after the effective date [^holland-amend-not-replace]. The common-law cases also mean that even old-law Wyoming covenants required careful drafting [^brown-baseline][^malave-baseline][^hassler-baseline].
|
|
177
181
|
|
|
@@ -183,7 +187,7 @@ Commentary specifically warns employers to evaluate routine replacement or updat
|
|
|
183
187
|
|
|
184
188
|
**July 1, 2025:** The new statute took effect for contracts entered into on or after that date. Earlier contracts were not altered, amended, or impaired by the act [^sf107-effective-date].
|
|
185
189
|
|
|
186
|
-
**2021–2022 backdrop:** Wyoming's common-law baseline was already demanding because of strict construction, consideration, and no-
|
|
190
|
+
**2021–2022 backdrop:** Wyoming's common-law baseline was already demanding because of strict construction, consideration, and no-narrowing cases [^brown-prima-facie][^malave-common-law-elements][^hassler-void-public-policy].
|
|
187
191
|
|
|
188
192
|
[^about]: By Steven Obiajulu, J.D. Published by [openagreements.org](https://openagreements.org) · Maintained by [UseJunior](https://usejunior.com). Last reviewed 2026-04-14. License: CC BY 4.0. Steven Obiajulu, J.D. is admitted in New York, not Wyoming. This article synthesizes Wyoming primary law and is not legal advice from a Wyoming-admitted attorney. This article is for informational purposes only and does not create an attorney-client relationship.
|
|
189
193
|
|
|
@@ -199,13 +203,11 @@ Commentary specifically warns employers to evaluate routine replacement or updat
|
|
|
199
203
|
|
|
200
204
|
[^holland-uphill-battle]: **Holland & Hart commentary** — "Employers still have an uphill battle to enforce a covenant not to compete in court." *Holland & Hart, Wyoming Legislature Takes a Bite Out of Covenants Not to Compete (2025).* <https://www.hollandhart.com/wyoming-legislature-takes-a-bite-out-of-covenants-not-to-compete-1>
|
|
201
205
|
|
|
202
|
-
[^
|
|
203
|
-
|
|
204
|
-
[^littler-any-status]: **Littler Mendelson commentary** — "The Act contains language broad enough to make most non-compete covenants with workers void regardless of a worker's status as an employee or an independent contractor" *Littler Mendelson, Wyoming Bans Non-Compete Covenants with Some Exceptions (2025).* <https://www.littler.com/news-analysis/asap/wyoming-bans-non-compete-covenants-some-exceptions>
|
|
206
|
+
[^sf107-prospective-savings]: **SF 107 § 2(b)** — "Nothing in this act shall be construed to alter, amend or impair any contract or agreement entered into before July 1, 2025." *S.F. 107, Enrolled Act No. 87, § 2(b), 68th Leg., Gen. Sess. (Wyo. 2025).* <https://wyoleg.gov/2025/Enroll/SF0107.pdf>
|
|
205
207
|
|
|
206
|
-
[^
|
|
208
|
+
[^malave-reasonableness-baseline]: **Malave v. Western Wyoming Beverages, Inc.** — "A valid and enforceable covenant not to compete requires a showing that the covenant is: (1) in writing; (2) part of a contract of employment; (3) based on reasonable consideration; (4) reasonable in durational and geographical limitations; and (5) not against public policy." *Malave v. Western Wyoming Beverages, Inc., 2022 WY 14, 503 P.3d 36.* <https://law.justia.com/cases/wyoming/supreme-court/2022/s-21-0140.html#:~:text=A%20valid%20and%20enforceable%20covenant,(5)%20not%20against%20public%20policy.>
|
|
207
209
|
|
|
208
|
-
[^
|
|
210
|
+
[^brown-strict-construction-baseline]: **Brown v. Best Home Health & Hospice, LLC** — "Contracts which hinder them from doing so are ‘strictly construed and rigidly scanned and are declared void unless necessary for the reasonable protection of the employer.’" *Brown v. Best Home Health & Hospice, LLC, 2021 WY 83, 491 P.3d 1021.* <https://www.courtlistener.com/opinion/9998787/jennifer-brown-fka-jennifer-stringer-nora-youngren-and-carol-wolfe-v/#:~:text=Contracts%20which%20hinder%20them%20from,reasonable%20protection%20of%20the%20employer.%22>
|
|
209
211
|
|
|
210
212
|
[^sf107-savings-clause]: **SF 107 § 2(b)** — "Nothing in this act shall be construed to alter, amend or impair any contract or agreement entered into before July 1, 2025." *S.F. 107, Enrolled Act No. 87, § 2(b), 68th Leg., Gen. Sess. (Wyo. 2025).* <https://wyoleg.gov/2025/Enroll/SF0107.pdf>
|
|
211
213
|
|
|
@@ -215,6 +217,14 @@ Commentary specifically warns employers to evaluate routine replacement or updat
|
|
|
215
217
|
|
|
216
218
|
[^brown-separate-consideration]: **Brown v. Best Home Health & Hospice, LLC** — "when an employer requests an existing employee sign a non-compete agreement, the employer must provide ‘separate contemporaneous consideration’ for the new promise" *Brown v. Best Home Health & Hospice, LLC, 2021 WY 83, 491 P.3d 1021.* <https://www.courtlistener.com/opinion/9998787/jennifer-brown-fka-jennifer-stringer-nora-youngren-and-carol-wolfe-v/#:~:text=when%20an%20employer%20requests%20an,consideration%22%20for%20the%20new%20promise>
|
|
217
219
|
|
|
220
|
+
[^wyo-1-23-any-person]: **Wyo. Stat. § 1-23-108(a)** — "Any covenant not to compete that restricts the right of any person to receive compensation for performance of skilled or unskilled labor shall be void." *Wyo. Stat. § 1-23-108(a) (2025).* <https://wyoleg.gov/2025/Enroll/SF0107.pdf>
|
|
221
|
+
|
|
222
|
+
[^littler-any-status]: **Littler Mendelson commentary** — "The Act contains language broad enough to make most non-compete covenants with workers void regardless of a worker's status as an employee or an independent contractor" *Littler Mendelson, Wyoming Bans Non-Compete Covenants with Some Exceptions (2025).* <https://www.littler.com/news-analysis/asap/wyoming-bans-non-compete-covenants-some-exceptions>
|
|
223
|
+
|
|
224
|
+
[^faegre-includes-contractors]: **Faegre Drinker commentary** — "Given that the law applies this restriction to agreements with any ‘person,’ this bans noncompete agreements with both employees and independent contractors" *Faegre Drinker, Wyoming Enacts Significant Restrictions on Noncompete Agreements (2025).* <https://www.faegredrinker.com/en/insights/publications/2025/3/wyoming-enacts-significant-restrictions-on-noncompete-agreements>
|
|
225
|
+
|
|
226
|
+
[^fisher-colorado-any-person]: **Fisher Phillips commentary** — "any covenant not to compete that restricts the right of any person to receive compensation for performance of skilled or unskilled labor...several provisions closely mirror language found in Colorado's prior non-compete statute" *Fisher Phillips, New Law Voids Most Wyoming Non-Compete Agreements (2025).* <https://www.fisherphillips.com/en/insights/insights/new-law-voids-most-wyoming-non-compete-agreements>
|
|
227
|
+
|
|
218
228
|
[^hassler-no-blue-pencil]: **Hassler v. Circle C Resources** — "Wyoming courts will no longer exceed the scope of their traditional authority in contract interpretation by redrafting noncompete agreements to bring them within the bounds of reason." *Hassler v. Circle C Resources, 2022 WY 28, 505 P.3d 169.* <https://www.courtlistener.com/opinion/9998701/charlene-hassler-v-circle-c-resources/#:~:text=Wyoming%20courts%20will%20no%20longer,within%20the%20bounds%20of%20reason.>
|
|
219
229
|
|
|
220
230
|
[^holland-blue-pencil-warning]: **Holland & Hart commentary** — "Since a 2022 Wyoming Supreme Court decision, Wyoming courts are no longer authorized to revise an unreasonable covenant to make it reasonable." *Holland & Hart, Wyoming Legislature Takes a Bite Out of Covenants Not to Compete (2025).* <https://www.hollandhart.com/wyoming-legislature-takes-a-bite-out-of-covenants-not-to-compete-1>
|
|
@@ -237,9 +247,13 @@ Commentary specifically warns employers to evaluate routine replacement or updat
|
|
|
237
247
|
|
|
238
248
|
[^fisher-nda-question]: **Fisher Phillips commentary** — "What is not clear, however, is whether other common forms of restrictive covenants will likewise be interpreted to constitute ‘covenants not to compete.’" *Fisher Phillips, New Law Voids Most Wyoming Non-Compete Agreements (2025).* <https://www.fisherphillips.com/en/insights/insights/new-law-voids-most-wyoming-non-compete-agreements>
|
|
239
249
|
|
|
240
|
-
[^wyo-1-23-
|
|
250
|
+
[^wyo-1-23-exec-staff]: **Wyo. Stat. § 1-23-108(a)(iv)** — "Executive and management personnel and officers and employees who constitute professional staff to executive and management personnel." *Wyo. Stat. § 1-23-108(a)(iv) (2025).* <https://wyoleg.gov/2025/Enroll/SF0107.pdf>
|
|
241
251
|
|
|
242
|
-
[^
|
|
252
|
+
[^faegre-exec-undefined]: **Faegre Drinker commentary** — "The statute does not define the terms ‘executive and personnel management’ or ‘professional staff,’ so which specific employees would qualify for this exemption is an open question" *Faegre Drinker, Wyoming Enacts Significant Restrictions on Noncompete Agreements (2025).* <https://www.faegredrinker.com/en/insights/publications/2025/3/wyoming-enacts-significant-restrictions-on-noncompete-agreements>
|
|
253
|
+
|
|
254
|
+
[^fisher-actual-duties]: **Fisher Phillips commentary** — "This analysis should focus on actual job responsibilities – not just job titles." *Fisher Phillips, New Law Voids Most Wyoming Non-Compete Agreements (2025).* <https://www.fisherphillips.com/en/insights/insights/new-law-voids-most-wyoming-non-compete-agreements>
|
|
255
|
+
|
|
256
|
+
[^holland-colorado-analogy]: **Holland & Hart commentary** — "Whether Wyoming courts will follow those definitions remains to be seen." *Holland & Hart, Wyoming Legislature Takes a Bite Out of Covenants Not to Compete (2025).* <https://www.hollandhart.com/wyoming-legislature-takes-a-bite-out-of-covenants-not-to-compete-1>
|
|
243
257
|
|
|
244
258
|
[^wyo-1-23-physician-bc]: **Wyo. Stat. § 1-23-108(b)–(c)** — "Any covenant not to compete provision of an employment, partnership or corporate agreement between physicians that restricts the right of a physician to practice medicine ... is void" *Wyo. Stat. § 1-23-108(b)–(c) (2025).* <https://wyoleg.gov/2025/Enroll/SF0107.pdf>
|
|
245
259
|
|
|
@@ -249,13 +263,9 @@ Commentary specifically warns employers to evaluate routine replacement or updat
|
|
|
249
263
|
|
|
250
264
|
[^holland-between-physicians]: **Holland & Hart commentary** — "This language suggests that the law intends to invalidate covenants not to compete entered into between physicians who are members of or employed by a medical practice owned by physicians, and not those contracts with hospitals or other types of entities." *Holland & Hart, Wyoming Legislature Takes a Bite Out of Covenants Not to Compete (2025).* <https://www.hollandhart.com/wyoming-legislature-takes-a-bite-out-of-covenants-not-to-compete-1>
|
|
251
265
|
|
|
252
|
-
[^wyo-1-23-
|
|
253
|
-
|
|
254
|
-
[^faegre-exec-undefined]: **Faegre Drinker commentary** — "The statute does not define the terms ‘executive and personnel management’ or ‘professional staff,’ so which specific employees would qualify for this exemption is an open question" *Faegre Drinker, Wyoming Enacts Significant Restrictions on Noncompete Agreements (2025).* <https://www.faegredrinker.com/en/insights/publications/2025/3/wyoming-enacts-significant-restrictions-on-noncompete-agreements>
|
|
255
|
-
|
|
256
|
-
[^fisher-actual-duties]: **Fisher Phillips commentary** — "This analysis should focus on actual job responsibilities – not just job titles." *Fisher Phillips, New Law Voids Most Wyoming Non-Compete Agreements (2025).* <https://www.fisherphillips.com/en/insights/insights/new-law-voids-most-wyoming-non-compete-agreements>
|
|
266
|
+
[^wyo-1-23-compensation-focus]: **Wyo. Stat. § 1-23-108(a)** — "Any covenant not to compete that restricts the right of any person to receive compensation for performance of skilled or unskilled labor shall be void." *Wyo. Stat. § 1-23-108(a) (2025).* <https://wyoleg.gov/2025/Enroll/SF0107.pdf>
|
|
257
267
|
|
|
258
|
-
[^
|
|
268
|
+
[^fisher-anti-moonlighting]: **Fisher Phillips commentary** — "For instance, will customer non-solicitation covenants fall into this definition? Employee non-solicitation covenants? Broad confidentiality agreements? ‘Anti-moonlighting’ agreements" *Fisher Phillips, New Law Voids Most Wyoming Non-Compete Agreements (2025).* <https://www.fisherphillips.com/en/insights/insights/new-law-voids-most-wyoming-non-compete-agreements>
|
|
259
269
|
|
|
260
270
|
[^wyo-1-23-repayment-schedule]: **Wyo. Stat. § 1-23-108(a)(iii)** — "Any contractual provision providing for the recovery of all or a portion of the expense of relocating, educating and training an employee as follows" *Wyo. Stat. § 1-23-108(a)(iii) (2025).* <https://wyoleg.gov/2025/Enroll/SF0107.pdf>
|
|
261
271
|
|