rift-desync 0.1.0__tar.gz

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.
Files changed (49) hide show
  1. rift_desync-0.1.0/LICENSE +201 -0
  2. rift_desync-0.1.0/PKG-INFO +335 -0
  3. rift_desync-0.1.0/README.md +93 -0
  4. rift_desync-0.1.0/pyproject.toml +121 -0
  5. rift_desync-0.1.0/setup.cfg +4 -0
  6. rift_desync-0.1.0/src/rift/__init__.py +21 -0
  7. rift_desync-0.1.0/src/rift/arsenal/__init__.py +4 -0
  8. rift_desync-0.1.0/src/rift/arsenal/demo.py +156 -0
  9. rift_desync-0.1.0/src/rift/arsenal/mcp_gateway.py +87 -0
  10. rift_desync-0.1.0/src/rift/cli.py +173 -0
  11. rift_desync-0.1.0/src/rift/controls/__init__.py +5 -0
  12. rift_desync-0.1.0/src/rift/controls/sanitizers.py +80 -0
  13. rift_desync-0.1.0/src/rift/defense/__init__.py +6 -0
  14. rift_desync-0.1.0/src/rift/defense/ctb.py +295 -0
  15. rift_desync-0.1.0/src/rift/defense/defense_benchmark.py +166 -0
  16. rift_desync-0.1.0/src/rift/defense/peg.py +118 -0
  17. rift_desync-0.1.0/src/rift/defense/repair_experiment.py +183 -0
  18. rift_desync-0.1.0/src/rift/defense/wsc_experiment.py +480 -0
  19. rift_desync-0.1.0/src/rift/defense/wsc_reader.py +189 -0
  20. rift_desync-0.1.0/src/rift/detector.py +112 -0
  21. rift_desync-0.1.0/src/rift/experiments/__init__.py +0 -0
  22. rift_desync-0.1.0/src/rift/experiments/benchmark_reader.py +97 -0
  23. rift_desync-0.1.0/src/rift/experiments/benchmark_suite.py +630 -0
  24. rift_desync-0.1.0/src/rift/experiments/field_study.py +248 -0
  25. rift_desync-0.1.0/src/rift/experiments/heldout_predictor.py +630 -0
  26. rift_desync-0.1.0/src/rift/experiments/heldout_reader.py +96 -0
  27. rift_desync-0.1.0/src/rift/experiments/live_sweep.py +566 -0
  28. rift_desync-0.1.0/src/rift/experiments/peg_vs_binding.py +273 -0
  29. rift_desync-0.1.0/src/rift/fuzzer/__init__.py +19 -0
  30. rift_desync-0.1.0/src/rift/fuzzer/content.py +226 -0
  31. rift_desync-0.1.0/src/rift/fuzzer/guards.py +256 -0
  32. rift_desync-0.1.0/src/rift/fuzzer/structural.py +98 -0
  33. rift_desync-0.1.0/src/rift/metrics/__init__.py +5 -0
  34. rift_desync-0.1.0/src/rift/metrics/benchmark.py +793 -0
  35. rift_desync-0.1.0/src/rift/metrics/precision.py +196 -0
  36. rift_desync-0.1.0/src/rift/py.typed +0 -0
  37. rift_desync-0.1.0/src/rift/shield.py +257 -0
  38. rift_desync-0.1.0/src/rift/theory/__init__.py +8 -0
  39. rift_desync-0.1.0/src/rift/theory/brier.py +166 -0
  40. rift_desync-0.1.0/src/rift/theory/equivalence_oracle.py +130 -0
  41. rift_desync-0.1.0/src/rift_desync.egg-info/PKG-INFO +335 -0
  42. rift_desync-0.1.0/src/rift_desync.egg-info/SOURCES.txt +47 -0
  43. rift_desync-0.1.0/src/rift_desync.egg-info/dependency_links.txt +1 -0
  44. rift_desync-0.1.0/src/rift_desync.egg-info/entry_points.txt +2 -0
  45. rift_desync-0.1.0/src/rift_desync.egg-info/requires.txt +20 -0
  46. rift_desync-0.1.0/src/rift_desync.egg-info/top_level.txt +1 -0
  47. rift_desync-0.1.0/tests/test_cli.py +45 -0
  48. rift_desync-0.1.0/tests/test_properties.py +48 -0
  49. rift_desync-0.1.0/tests/test_smoke.py +281 -0
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or Derivative
95
+ Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright 2026 Yuvraj Pradhan
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
@@ -0,0 +1,335 @@
1
+ Metadata-Version: 2.4
2
+ Name: rift-desync
3
+ Version: 0.1.0
4
+ Summary: Find the rift between an LLM agent guard's parse and the executor's. Guardrail Desync predictor + parse-equivalence gate.
5
+ Author-email: Yuvraj Pradhan <yuvraj0227@gmail.com>
6
+ License: Apache License
7
+ Version 2.0, January 2004
8
+ http://www.apache.org/licenses/
9
+
10
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
11
+
12
+ 1. Definitions.
13
+
14
+ "License" shall mean the terms and conditions for use, reproduction,
15
+ and distribution as defined by Sections 1 through 9 of this document.
16
+
17
+ "Licensor" shall mean the copyright owner or entity authorized by
18
+ the copyright owner that is granting the License.
19
+
20
+ "Legal Entity" shall mean the union of the acting entity and all
21
+ other entities that control, are controlled by, or are under common
22
+ control with that entity. For the purposes of this definition,
23
+ "control" means (i) the power, direct or indirect, to cause the
24
+ direction or management of such entity, whether by contract or
25
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
26
+ outstanding shares, or (iii) beneficial ownership of such entity.
27
+
28
+ "You" (or "Your") shall mean an individual or Legal Entity
29
+ exercising permissions granted by this License.
30
+
31
+ "Source" form shall mean the preferred form for making modifications,
32
+ including but not limited to software source code, documentation
33
+ source, and configuration files.
34
+
35
+ "Object" form shall mean any form resulting from mechanical
36
+ transformation or translation of a Source form, including but
37
+ not limited to compiled object code, generated documentation,
38
+ and conversions to other media types.
39
+
40
+ "Work" shall mean the work of authorship, whether in Source or
41
+ Object form, made available under the License, as indicated by a
42
+ copyright notice that is included in or attached to the work
43
+ (an example is provided in the Appendix below).
44
+
45
+ "Derivative Works" shall mean any work, whether in Source or Object
46
+ form, that is based on (or derived from) the Work and for which the
47
+ editorial revisions, annotations, elaborations, or other modifications
48
+ represent, as a whole, an original work of authorship. For the purposes
49
+ of this License, Derivative Works shall not include works that remain
50
+ separable from, or merely link (or bind by name) to the interfaces of,
51
+ the Work and Derivative Works thereof.
52
+
53
+ "Contribution" shall mean any work of authorship, including
54
+ the original version of the Work and any modifications or additions
55
+ to that Work or Derivative Works thereof, that is intentionally
56
+ submitted to Licensor for inclusion in the Work by the copyright owner
57
+ or by an individual or Legal Entity authorized to submit on behalf of
58
+ the copyright owner. For the purposes of this definition, "submitted"
59
+ means any form of electronic, verbal, or written communication sent
60
+ to the Licensor or its representatives, including but not limited to
61
+ communication on electronic mailing lists, source code control systems,
62
+ and issue tracking systems that are managed by, or on behalf of, the
63
+ Licensor for the purpose of discussing and improving the Work, but
64
+ excluding communication that is conspicuously marked or otherwise
65
+ designated in writing by the copyright owner as "Not a Contribution."
66
+
67
+ "Contributor" shall mean Licensor and any individual or Legal Entity
68
+ on behalf of whom a Contribution has been received by Licensor and
69
+ subsequently incorporated within the Work.
70
+
71
+ 2. Grant of Copyright License. Subject to the terms and conditions of
72
+ this License, each Contributor hereby grants to You a perpetual,
73
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
74
+ copyright license to reproduce, prepare Derivative Works of,
75
+ publicly display, publicly perform, sublicense, and distribute the
76
+ Work and such Derivative Works in Source or Object form.
77
+
78
+ 3. Grant of Patent License. Subject to the terms and conditions of
79
+ this License, each Contributor hereby grants to You a perpetual,
80
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
81
+ (except as stated in this section) patent license to make, have made,
82
+ use, offer to sell, sell, import, and otherwise transfer the Work,
83
+ where such license applies only to those patent claims licensable
84
+ by such Contributor that are necessarily infringed by their
85
+ Contribution(s) alone or by combination of their Contribution(s)
86
+ with the Work to which such Contribution(s) was submitted. If You
87
+ institute patent litigation against any entity (including a
88
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
89
+ or a Contribution incorporated within the Work constitutes direct
90
+ or contributory patent infringement, then any patent licenses
91
+ granted to You under this License for that Work shall terminate
92
+ as of the date such litigation is filed.
93
+
94
+ 4. Redistribution. You may reproduce and distribute copies of the
95
+ Work or Derivative Works thereof in any medium, with or without
96
+ modifications, and in Source or Object form, provided that You
97
+ meet the following conditions:
98
+
99
+ (a) You must give any other recipients of the Work or Derivative
100
+ Works a copy of this License; and
101
+
102
+ (b) You must cause any modified files to carry prominent notices
103
+ stating that You changed the files; and
104
+
105
+ (c) You must retain, in the Source form of any Derivative Works
106
+ that You distribute, all copyright, patent, trademark, and
107
+ attribution notices from the Source form of the Work,
108
+ excluding those notices that do not pertain to any part of
109
+ the Derivative Works; and
110
+
111
+ (d) If the Work includes a "NOTICE" text file as part of its
112
+ distribution, then any Derivative Works that You distribute must
113
+ include a readable copy of the attribution notices contained
114
+ within such NOTICE file, excluding those notices that do not
115
+ pertain to any part of the Derivative Works, in at least one
116
+ of the following places: within a NOTICE text file distributed
117
+ as part of the Derivative Works; within the Source form or
118
+ documentation, if provided along with the Derivative Works; or,
119
+ within a display generated by the Derivative Works, if and
120
+ wherever such third-party notices normally appear. The contents
121
+ of the NOTICE file are for informational purposes only and
122
+ do not modify the License. You may add Your own attribution
123
+ notices within Derivative Works that You distribute, alongside
124
+ or as an addendum to the NOTICE text from the Work, provided
125
+ that such additional attribution notices cannot be construed
126
+ as modifying the License.
127
+
128
+ You may add Your own copyright statement to Your modifications and
129
+ may provide additional or different license terms and conditions
130
+ for use, reproduction, or distribution of Your modifications, or
131
+ for any such Derivative Works as a whole, provided Your use,
132
+ reproduction, and distribution of the Work otherwise complies with
133
+ the conditions stated in this License.
134
+
135
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
136
+ any Contribution intentionally submitted for inclusion in the Work
137
+ by You to the Licensor shall be under the terms and conditions of
138
+ this License, without any additional terms or conditions.
139
+ Notwithstanding the above, nothing herein shall supersede or modify
140
+ the terms of any separate license agreement you may have executed
141
+ with Licensor regarding such Contributions.
142
+
143
+ 6. Trademarks. This License does not grant permission to use the trade
144
+ names, trademarks, service marks, or product names of the Licensor,
145
+ except as required for reasonable and customary use in describing the
146
+ origin of the Work and reproducing the content of the NOTICE file.
147
+
148
+ 7. Disclaimer of Warranty. Unless required by applicable law or
149
+ agreed to in writing, Licensor provides the Work (and each
150
+ Contributor provides its Contributions) on an "AS IS" BASIS,
151
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
152
+ implied, including, without limitation, any warranties or conditions
153
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
154
+ PARTICULAR PURPOSE. You are solely responsible for determining the
155
+ appropriateness of using or redistributing the Work and assume any
156
+ risks associated with Your exercise of permissions under this License.
157
+
158
+ 8. Limitation of Liability. In no event and under no legal theory,
159
+ whether in tort (including negligence), contract, or otherwise,
160
+ unless required by applicable law (such as deliberate and grossly
161
+ negligent acts) or agreed to in writing, shall any Contributor be
162
+ liable to You for damages, including any direct, indirect, special,
163
+ incidental, or consequential damages of any character arising as a
164
+ result of this License or out of the use or inability to use the
165
+ Work (including but not limited to damages for loss of goodwill,
166
+ work stoppage, computer failure or malfunction, or any and all
167
+ other commercial damages or losses), even if such Contributor
168
+ has been advised of the possibility of such damages.
169
+
170
+ 9. Accepting Warranty or Additional Liability. While redistributing
171
+ the Work or Derivative Works thereof, You may choose to offer,
172
+ and charge a fee for, acceptance of support, warranty, indemnity,
173
+ or other liability obligations and/or rights consistent with this
174
+ License. However, in accepting such obligations, You may act only
175
+ on Your own behalf and on Your sole responsibility, not on behalf
176
+ of any other Contributor, and only if You agree to indemnify,
177
+ defend, and hold each Contributor harmless for any liability
178
+ incurred by, or claims asserted against, such Contributor by reason
179
+ of your accepting any such warranty or additional liability.
180
+
181
+ END OF TERMS AND CONDITIONS
182
+
183
+ APPENDIX: How to apply the Apache License to your work.
184
+
185
+ To apply the Apache License to your work, attach the following
186
+ boilerplate notice, with the fields enclosed by brackets "[]"
187
+ replaced with your own identifying information. (Don't include
188
+ the brackets!) The text should be enclosed in the appropriate
189
+ comment syntax for the file format. We also recommend that a
190
+ file or class name and description of purpose be included on the
191
+ same "printed page" as the copyright notice for easier
192
+ identification within third-party archives.
193
+
194
+ Copyright 2026 Yuvraj Pradhan
195
+
196
+ Licensed under the Apache License, Version 2.0 (the "License");
197
+ you may not use this file except in compliance with the License.
198
+ You may obtain a copy of the License at
199
+
200
+ http://www.apache.org/licenses/LICENSE-2.0
201
+
202
+ Unless required by applicable law or agreed to in writing, software
203
+ distributed under the License is distributed on an "AS IS" BASIS,
204
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
205
+ See the License for the specific language governing permissions and
206
+ limitations under the License.
207
+
208
+ Project-URL: Homepage, https://github.com/Uvi-12/rift
209
+ Project-URL: Source, https://github.com/Uvi-12/rift
210
+ Project-URL: Issues, https://github.com/Uvi-12/rift/issues
211
+ Keywords: security,llm,agent,guardrails,parser-differential,request-smuggling,appsec
212
+ Classifier: Intended Audience :: Developers
213
+ Classifier: Topic :: Security
214
+ Classifier: License :: OSI Approved :: Apache Software License
215
+ Classifier: Programming Language :: Python :: 3
216
+ Classifier: Programming Language :: Python :: 3.10
217
+ Classifier: Programming Language :: Python :: 3.11
218
+ Classifier: Programming Language :: Python :: 3.12
219
+ Classifier: Programming Language :: Python :: 3.13
220
+ Classifier: Typing :: Typed
221
+ Requires-Python: >=3.10
222
+ Description-Content-Type: text/markdown
223
+ License-File: LICENSE
224
+ Provides-Extra: guards
225
+ Requires-Dist: llm-guard; extra == "guards"
226
+ Requires-Dist: detect-secrets; extra == "guards"
227
+ Requires-Dist: presidio-analyzer; extra == "guards"
228
+ Requires-Dist: nemoguardrails; extra == "guards"
229
+ Requires-Dist: pyyaml; extra == "guards"
230
+ Provides-Extra: sanitizers
231
+ Requires-Dist: bleach; extra == "sanitizers"
232
+ Requires-Dist: nh3; extra == "sanitizers"
233
+ Provides-Extra: dev
234
+ Requires-Dist: ruff>=0.6; extra == "dev"
235
+ Requires-Dist: mypy>=1.10; extra == "dev"
236
+ Requires-Dist: pytest>=7; extra == "dev"
237
+ Requires-Dist: pytest-cov>=5; extra == "dev"
238
+ Requires-Dist: hypothesis>=6; extra == "dev"
239
+ Requires-Dist: build>=1; extra == "dev"
240
+ Requires-Dist: pre-commit>=3; extra == "dev"
241
+ Dynamic: license-file
242
+
243
+ # rift
244
+
245
+ [![CI](https://github.com/Uvi-12/rift/actions/workflows/ci.yml/badge.svg)](https://github.com/Uvi-12/rift/actions/workflows/ci.yml)
246
+ [![PyPI](https://img.shields.io/pypi/v/rift-desync.svg)](https://pypi.org/project/rift-desync/)
247
+ [![Python](https://img.shields.io/pypi/pyversions/rift-desync.svg)](https://pypi.org/project/rift-desync/)
248
+ [![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
249
+
250
+ Find the rift between an LLM agent guard's parse and the executor's, before it runs.
251
+
252
+ An agent screens a dangerous action behind a guard: a check that decides if a command, path, URL, or SQL string is safe. The thing that actually runs it parses the same bytes differently. When they disagree, you hand them one input: the guard clears it, the executor runs it as the hazard. The model never touches that gap, so a perfectly aligned model does not close it. This is the agent-boundary cousin of HTTP request smuggling. The research calls the class Guardrail Desync.
253
+
254
+ `rift` reads a guard's source and tells you which side it is on, before you send a single payload.
255
+
256
+ - **DELEGATE**: the guard routes its whole decision through the executor's own parser. It holds.
257
+ - **REIMPLEMENT**: the guard decides on a hand-rolled view, a regex, a token blocklist, a lexical path check. There is a rift, and it is desync-prone.
258
+
259
+ That prediction is not a hunch. It is measured on a benchmark, corroborated on real deployed guards, and the underlying law is proved in Coq.
260
+
261
+ ## Install
262
+
263
+ ```
264
+ pip install rift-desync
265
+ ```
266
+
267
+ The distribution is `rift-desync` (the name `rift` was taken on PyPI); the import package and the command are both `rift`. Stdlib only for the core. The optional extras pull in real guard libraries you want to test.
268
+
269
+ > **`rift scan` imports and executes the guard module you point it at.** That is by design, it has to call the guard to read its structure, but it means you should only run it on guard code you trust and installed yourself.
270
+
271
+ ## Quick start
272
+
273
+ Point it at a guard function and name the boundary it defends:
274
+
275
+ ```
276
+ $ rift scan examples/shell_reimplement.py --boundary shell
277
+ guard guard (examples/shell_reimplement.py)
278
+ boundary shell
279
+ verdict REIMPLEMENT
280
+ the guard decides on a hand-rolled view, not the executor's parse.
281
+ predicted DESYNC-PRONE: an input the guard admits can carry a
282
+ differential the executor runs as a hazard.
283
+ ```
284
+
285
+ ```
286
+ $ rift scan examples/shell_delegate.py --boundary shell
287
+ verdict DELEGATE
288
+ the guard routes its whole decision through the executor's parser.
289
+ predicted SAFE under the law (no hazard-relevant differential).
290
+ ```
291
+
292
+ Boundaries: `shell`, `url`, `path`, `sql`, `content`. Write your guard as a function `guard(x) -> bool` (True means the guard admits x), or pass `--guard NAME`.
293
+
294
+ ## The fix: PEG
295
+
296
+ The repair is to stop re-implementing the parser. The Parse-Equivalence Gate runs the guard against every parse the executor could take and admits only when they all agree, so it inherits the executor's transforms by construction and cannot be out-enumerated.
297
+
298
+ ```
299
+ $ rift peg
300
+ ```
301
+
302
+ Against a canonicalize-then-bind comparator on the SSRF and content boundaries, PEG admits 0 of the hazards that ctb leaks, with no false positives:
303
+
304
+ ```
305
+ ctb (finite canonicalizer): 5 hazardous input(s) ADMITTED (bypass).
306
+ PEG (no canonicalizer): 0 hazardous input(s) admitted; 0 benign wrongly rejected.
307
+ ```
308
+
309
+ The leaks are three loopback short forms (`127.1`, `127.0.1`, `0x7f.1`, which `inet_aton` dials but a strict decoder rejects) and two Cyrillic confusables that NFKC does not fold.
310
+
311
+ ## The evidence
312
+
313
+ ```
314
+ rift bench # 140 guards, 22,732 comparisons: held-out phi +0.66 vs -0.05 naive baseline
315
+ rift field # the predictor on 9 real pip-installable guards: 9 of 9, zero delegate-but-fall
316
+ rift peg # PEG vs canonicalize-then-bind: ctb leaks 5, PEG admits 0, no false positives
317
+ rift proof # the Coq law: 0 axioms, 8 closed proofs
318
+ rift reproduce # all of the above in one pass (make reproduce)
319
+ ```
320
+
321
+ Install the guard extras for the full field study: `pip install "rift-desync[guards]"`.
322
+
323
+ - **Benchmark.** On 140 built guards across 22,732 comparisons, the source-read delegate-vs-reimplement call separates safe from broken on held-out boundaries at phi +0.66, against -0.05 for a baseline that only asks whether a guard calls a parser at all. Delegate implies safe at precision 1.000, with zero delegating-but-unsafe guards.
324
+ - **Field study.** The same structural call, applied to the real installed source of nine deployed guards (bleach, defusedxml, the MCP SDK, cli-mcp-server, validators, detect-secrets, guardrails-ai, presidio, NeMo Guardrails), agrees with each guard's independently measured disposition on 9 of 9, with zero delegate-but-fall, the only kind of case that would refute the law.
325
+ - **The law.** Coq 8.18, no axioms, eight closed proofs. Delegating to the executor's parse is safe; a guard that maps a permitted and a forbidden request onto one value stays safe only by rejecting both; PEG covers the canonicalizer gap. `coqc proofs/RIFT.v` checks it green.
326
+
327
+ The predictor is deliberately fallible. The corpus includes guards that delegate to the wrong parser and re-implementers that hold only by being over-restrictive, and every off-diagonal case is reported rather than dropped. A predictor that scored 100% here would be a red flag, not a result.
328
+
329
+ ## Coordinated disclosure
330
+
331
+ This tool came out of breaking real shipped agents. Those findings are handled under coordinated disclosure with the maintainers. This repository contains the predictor, the gate, the benchmark, the studies, and the proof. It does not contain working exploit payloads for embargoed findings or any vendor-specific zero-day. Advisory identifiers and proofs-of-concept move through the vendors' own channels, not here.
332
+
333
+ ## License
334
+
335
+ Apache-2.0. See `LICENSE`.
@@ -0,0 +1,93 @@
1
+ # rift
2
+
3
+ [![CI](https://github.com/Uvi-12/rift/actions/workflows/ci.yml/badge.svg)](https://github.com/Uvi-12/rift/actions/workflows/ci.yml)
4
+ [![PyPI](https://img.shields.io/pypi/v/rift-desync.svg)](https://pypi.org/project/rift-desync/)
5
+ [![Python](https://img.shields.io/pypi/pyversions/rift-desync.svg)](https://pypi.org/project/rift-desync/)
6
+ [![License](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)
7
+
8
+ Find the rift between an LLM agent guard's parse and the executor's, before it runs.
9
+
10
+ An agent screens a dangerous action behind a guard: a check that decides if a command, path, URL, or SQL string is safe. The thing that actually runs it parses the same bytes differently. When they disagree, you hand them one input: the guard clears it, the executor runs it as the hazard. The model never touches that gap, so a perfectly aligned model does not close it. This is the agent-boundary cousin of HTTP request smuggling. The research calls the class Guardrail Desync.
11
+
12
+ `rift` reads a guard's source and tells you which side it is on, before you send a single payload.
13
+
14
+ - **DELEGATE**: the guard routes its whole decision through the executor's own parser. It holds.
15
+ - **REIMPLEMENT**: the guard decides on a hand-rolled view, a regex, a token blocklist, a lexical path check. There is a rift, and it is desync-prone.
16
+
17
+ That prediction is not a hunch. It is measured on a benchmark, corroborated on real deployed guards, and the underlying law is proved in Coq.
18
+
19
+ ## Install
20
+
21
+ ```
22
+ pip install rift-desync
23
+ ```
24
+
25
+ The distribution is `rift-desync` (the name `rift` was taken on PyPI); the import package and the command are both `rift`. Stdlib only for the core. The optional extras pull in real guard libraries you want to test.
26
+
27
+ > **`rift scan` imports and executes the guard module you point it at.** That is by design, it has to call the guard to read its structure, but it means you should only run it on guard code you trust and installed yourself.
28
+
29
+ ## Quick start
30
+
31
+ Point it at a guard function and name the boundary it defends:
32
+
33
+ ```
34
+ $ rift scan examples/shell_reimplement.py --boundary shell
35
+ guard guard (examples/shell_reimplement.py)
36
+ boundary shell
37
+ verdict REIMPLEMENT
38
+ the guard decides on a hand-rolled view, not the executor's parse.
39
+ predicted DESYNC-PRONE: an input the guard admits can carry a
40
+ differential the executor runs as a hazard.
41
+ ```
42
+
43
+ ```
44
+ $ rift scan examples/shell_delegate.py --boundary shell
45
+ verdict DELEGATE
46
+ the guard routes its whole decision through the executor's parser.
47
+ predicted SAFE under the law (no hazard-relevant differential).
48
+ ```
49
+
50
+ Boundaries: `shell`, `url`, `path`, `sql`, `content`. Write your guard as a function `guard(x) -> bool` (True means the guard admits x), or pass `--guard NAME`.
51
+
52
+ ## The fix: PEG
53
+
54
+ The repair is to stop re-implementing the parser. The Parse-Equivalence Gate runs the guard against every parse the executor could take and admits only when they all agree, so it inherits the executor's transforms by construction and cannot be out-enumerated.
55
+
56
+ ```
57
+ $ rift peg
58
+ ```
59
+
60
+ Against a canonicalize-then-bind comparator on the SSRF and content boundaries, PEG admits 0 of the hazards that ctb leaks, with no false positives:
61
+
62
+ ```
63
+ ctb (finite canonicalizer): 5 hazardous input(s) ADMITTED (bypass).
64
+ PEG (no canonicalizer): 0 hazardous input(s) admitted; 0 benign wrongly rejected.
65
+ ```
66
+
67
+ The leaks are three loopback short forms (`127.1`, `127.0.1`, `0x7f.1`, which `inet_aton` dials but a strict decoder rejects) and two Cyrillic confusables that NFKC does not fold.
68
+
69
+ ## The evidence
70
+
71
+ ```
72
+ rift bench # 140 guards, 22,732 comparisons: held-out phi +0.66 vs -0.05 naive baseline
73
+ rift field # the predictor on 9 real pip-installable guards: 9 of 9, zero delegate-but-fall
74
+ rift peg # PEG vs canonicalize-then-bind: ctb leaks 5, PEG admits 0, no false positives
75
+ rift proof # the Coq law: 0 axioms, 8 closed proofs
76
+ rift reproduce # all of the above in one pass (make reproduce)
77
+ ```
78
+
79
+ Install the guard extras for the full field study: `pip install "rift-desync[guards]"`.
80
+
81
+ - **Benchmark.** On 140 built guards across 22,732 comparisons, the source-read delegate-vs-reimplement call separates safe from broken on held-out boundaries at phi +0.66, against -0.05 for a baseline that only asks whether a guard calls a parser at all. Delegate implies safe at precision 1.000, with zero delegating-but-unsafe guards.
82
+ - **Field study.** The same structural call, applied to the real installed source of nine deployed guards (bleach, defusedxml, the MCP SDK, cli-mcp-server, validators, detect-secrets, guardrails-ai, presidio, NeMo Guardrails), agrees with each guard's independently measured disposition on 9 of 9, with zero delegate-but-fall, the only kind of case that would refute the law.
83
+ - **The law.** Coq 8.18, no axioms, eight closed proofs. Delegating to the executor's parse is safe; a guard that maps a permitted and a forbidden request onto one value stays safe only by rejecting both; PEG covers the canonicalizer gap. `coqc proofs/RIFT.v` checks it green.
84
+
85
+ The predictor is deliberately fallible. The corpus includes guards that delegate to the wrong parser and re-implementers that hold only by being over-restrictive, and every off-diagonal case is reported rather than dropped. A predictor that scored 100% here would be a red flag, not a result.
86
+
87
+ ## Coordinated disclosure
88
+
89
+ This tool came out of breaking real shipped agents. Those findings are handled under coordinated disclosure with the maintainers. This repository contains the predictor, the gate, the benchmark, the studies, and the proof. It does not contain working exploit payloads for embargoed findings or any vendor-specific zero-day. Advisory identifiers and proofs-of-concept move through the vendors' own channels, not here.
90
+
91
+ ## License
92
+
93
+ Apache-2.0. See `LICENSE`.