
Research
Malicious fezbox npm Package Steals Browser Passwords from Cookies via Innovative QR Code Steganographic Technique
A malicious package uses a QR code as steganography in an innovative technique.
model-checker
Advanced tools
A hyperintensional theorem prover for developing and and exploring programmatic semantic theories.
← GitHub Repository | General Docs → | Technical Docs →
A programmatic framework for implementing modular semantic theories powered by the Z3 SMT solver.
Install the package:
pip install model-checker
For development:
git clone https://github.com/benbrastmckie/ModelChecker.git
cd ModelChecker/Code
pip install -e .
NixOS users: Use nix-shell instead. See NixOS Development.
For complete installation guides, see Installation Documentation.
Create a new logic project:
model-checker -l logos # Hyperintensional logic
model-checker -l exclusion # Unilateral semantics
model-checker -l imposition # Fine's counterfactuals
model-checker -l bimodal # Temporal-modal logic
ModelChecker is a theory-agnostic framework that allows researchers to implement, test, and share semantic theories for logical reasoning. The TheoryLib provides a collection of pre-built theories that can be used directly, modified for specific needs, or serve as templates for developing new theories. Users can upload their own theories to share with the community, fostering collaborative development of computational semantics.
The Logos Semantics provides a bilateral semantics for a formal language of thought, implementing hyperintensional distinctions through verifier and falsifier sets. This approach enables the framework to distinguish between propositions that are necessarily equivalent but differ in content which is critical for modeling fine-grained reasoning about counterfactuals and explanatory operators.
Logos currently includes operators organized into modular subtheories:
∧, ∨, ¬, →, ↔, ⊤, ⊥)□, ◇)□→, ◇→)≤, ⊑, ≡)≼)The modular architecture allows users to load only the operators needed for their analysis, with automatic dependency resolution ensuring semantic coherence. Additional operators are actively being developed, expanding the theory's expressiveness for new applications in philosophy, logic, and cognitive science.
The framework defines semantic theories by extending the base SemanticDefaults class:
class LogosSemantics(SemanticDefaults):
def __init__(self, combined_settings):
super().__init__(combined_settings)
# Core attributes
self.N = combined_settings['N'] # Bit-width for states
self.all_states = [BitVecVal(i, self.N) for i in range(1 << self.N)]
self.null_state = BitVecVal(0, self.N)
self.full_state = BitVecVal((1 << self.N) - 1, self.N)
# Z3 function declarations
self.verify = z3.Function("verify", BitVecSort(self.N), AtomSort, BoolSort())
self.falsify = z3.Function("falsify", BitVecSort(self.N), AtomSort, BoolSort())
self.possible = z3.Function("possible", BitVecSort(self.N), BoolSort())
# Evaluation point
self.main_world = z3.BitVec("w", self.N)
self.main_point = {"world": self.main_world}
# self.main_time = z3.IntVal(0) # Under construction in bimodal/
# self.main_point = {"world": self.main_world, "time": self.main_time}
# Frame constraints
self.frame_constraints = [self.is_world(self.main_world), ...]
def fusion(self, bit_s, bit_t):
"""Combines two states using bitwise OR."""
return bit_s | bit_t
def is_part_of(self, bit_s, bit_t):
"""Tests if bit_s is a part of bit_t."""
return (bit_s & bit_t) == bit_s
def compatible(self, state_x, state_y):
"""Determines if the fusion of two states is possible."""
return self.possible(self.fusion(state_x, state_y))
def is_world(self, state_w):
"""Determines if a state is a possible world (possible and maximal)."""
return z3.And(
self.possible(state_w),
self.maximal(state_w)
)
def true_at(self, sentence, eval_point):
"""Evaluates if sentence is true at eval_point.
For atoms: `∃x ⊆ w: verify(x, atom)`
For complex: delegates to operator.true_at()"""
eval_world = eval_point["world"]
if sentence.sentence_letter is not None:
x = z3.BitVec("t_atom_x", self.N)
return Exists(x, z3.And(
self.is_part_of(x, eval_world),
self.verify(x, sentence.sentence_letter)
))
return sentence.operator.true_at(*sentence.arguments, eval_point)
def extended_verify(self, state, sentence, eval_point):
"""Tests if state verifies sentence.
For atoms: verify(state, atom)
For complex: delegates to operator.extended_verify()"""
if sentence.sentence_letter is not None:
return self.verify(state, sentence.sentence_letter)
return sentence.operator.extended_verify(
state, *sentence.arguments, eval_point
)
def is_alternative(self, u, x, w):
"""Tests if u is an x-alternative to w.
Used in counterfactual evaluation."""
# Implementation varies by theory
# Example: u is world where `x ∨ (w ∧ ¬x)` is maximal
The framework provides modular operators across five subtheories:
¬ - Negation (swaps verifiers/falsifiers)∧ - Conjunction (fuses verifiers, distributes falsifiers)∨ - Disjunction (distributes verifiers, fuses falsifiers)→ - Material conditional↔ - Biconditional⊤ - Tautology (always true)⊥ - Contradiction (always false)□ - Necessity (true at all worlds)◇ - Possibility (true at some world)□→ - Would counterfactual◇→ - Might counterfactual≤ - Grounding (A grounds B)⊑ - Essence (A is essential to B)≡ - Constitutive equivalenceThe counterfactual operator (□→) demonstrates the framework's approach:
def true_at(self, leftarg, rightarg, eval_point):
"""A `□→` B is true at w iff:
For all verifiers x of A and all x-alternatives u to w,
B is true at u"""
return ForAll([x, u],
Implies(
And(extended_verify(x, leftarg, eval_point),
is_alternative(u, x, eval_point["world"])),
true_at(rightarg, {"world": u})
))
def false_at(self, leftarg, rightarg, eval_point):
"""A `□→` B is false at w iff:
There exists a verifier x of A and x-alternative u to w
where B is false at u"""
return Exists([x, u],
And(extended_verify(x, leftarg, eval_point),
is_alternative(u, x, eval_point["world"]),
false_at(rightarg, {"world": u})))
This implementation captures the hyperintensional nature of counterfactuals - the alternative worlds depend on which specific verifier of the antecedent we consider.
Each semantic theory includes an examples.py module with a range of examples. The following subsection will focus on counterfactual conditionals.
Example 1: Counterfactual Antecedent Strengthening (Invalid)
# Enable specific examples in examples.py
example_range = {
"CF_CM_1": CF_CM_1_example, # Antecedent strengthening
"CF_TH_5": CF_TH_5_example, # Simplification of disjunctive antecedent
}
# Run the examples
./dev_cli.py src/model_checker/theory_lib/logos/subtheories/counterfactual/examples.py
Output for CF_CM_1:
EXAMPLE CF_CM_1: there is a countermodel.
Premises:
1. `¬A`
2. `(A □→ C)`
Conclusion:
3. `((A ∧ B) □→ C)`
The evaluation world is: b.c
INTERPRETED PREMISES:
1. `|¬A| = < {b.c}, {a, a.b.c.d} >` (True in b.c)
2. `|(A □→ C)| = < {a.c, b.c}, {a.d} >` (True in b.c)
`|A|`-alternatives to b.c = {a.c}
`|C| = < {a.c}, {a.b.c.d, a.b.d, a.d, b} >` (True in a.c)
INTERPRETED CONCLUSION:
3. `|((A ∧ B) □→ C)| = < {}, {a.c, a.d, b.c} >` (False in b.c)
`|(A ∧ B)|`-alternatives to b.c = {a.d}
`|C| = < {a.c}, {a.b.c.d, a.b.d, a.d, b} >` (False in a.d)
This shows that "If A were true then C" doesn't entail "If A and B were true then C" since the additional condition B can change which alternatives are relevant to quantify over. For instance, just the match would light if it were struck, it does not follow that it would light if struck when wet.
Example 2: Simplification of Disjunctive Antecedent (Valid Theorem)
Output for CF_TH_5:
EXAMPLE CF_TH_5: there is no countermodel.
Premise:
1. `((A ∨ B) □→ C)`
Conclusion:
2. `(A □→ C)`
Z3 Run Time: 0.0342 seconds
This theorem shows that counterfactuals satisfy simplification of disjunctive antecedent: assuming C would be the case if either A or B were the case, it follows that C would be the case if A alone were the case (similarly for for B).
To run specific examples from a theory:
example_range dictionary in the theory's examples.py file./dev_cli.py src/model_checker/theory_lib/logos/subtheories/[subtheory]/examples.py
'iterate': n in settings to find up to n distinct modelssemantic_theories dictionary'print_constraints': True to see Z3 constraints'print_impossible': True to examine impossible states'print_z3': True for raw solver output'save_output': True to save results to file'maximize': True to compare theories systematicallyFor comprehensive guidance on theory comparison, avoiding circular imports, and advanced multi-theory setups, see Theory Comparison Guide.
We welcome contributions! See our GitHub repository for:
If you use ModelChecker in your research, please cite:
GPL-3.0 - see LICENSE for details.
ModelChecker provides a framework for developing, testing, and comparing semantic theories for logical operators. The current implementation focuses on the objective fragment of the language, with operators for:
∧, ∨, ¬, →, ↔)□, ◇)□→, ◇→)≤, ⊑, ≡)The framework currently implements operators from the objective language, with normative and epistemic operators planned for future development. Each theory can be:
The bimodal theory provides a purely intensional treatment of temporal and modal operators, where worlds are functions from times to world states that respect a primitive task relation that specifies which transitions between states are possible.
Future work will integrate this temporal dimension into the Logos framework, completing the implementation of the hyperintensional semantics developed in Brast-McKie (2025).
Use ModelChecker to:
The framework serves as a research tool for computational semantics and a testing ground for theories about modality, counterfactuals, grounding, and time.
FAQs
A hyperintensional theorem prover for developing and and exploring programmatic semantic theories.
We found that model-checker demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Research
A malicious package uses a QR code as steganography in an innovative technique.

Research
/Security News
Socket identified 80 fake candidates targeting engineering roles, including suspected North Korean operators, exposing the new reality of hiring as a security function.

Application Security
/Research
/Security News
Socket detected multiple compromised CrowdStrike npm packages, continuing the "Shai-Hulud" supply chain attack that has now impacted nearly 500 packages.