How duraki/frida-cycript works
Main Components
a. Core Components:
• Compiler System (cylang to JavaScript)
• Mjølner Runtime (Frida-powered)
• Console Interface
• Node.js Bindings
b. Supporting Components:
• Parser Components (Bison/Flex)
• Bridge System
• Analysis Engine
• External Dependencies (Frida, readline)
┌─────────────────────────────────────────┐
• User Interface │
• (Console/REPL, Node.js Bindings) │
• ┤
• Compiler Layer │
• (Parser, Scanner, Syntax Analysis) │
• ┤
• Runtime Layer │
• (Mjølner/Frida Runtime, Bridge) │
• ┤
• Target Application │
• (iOS/Android/macOS/Windows Process) │
• ┘
Component Details
• Rectangles: Main components
• Hexagons: External dependencies
Key Relationships
a. Input Flow:
• User input → Console Interface
• Console → Compiler (cylang code)
• Compiler → JavaScript output
b. Runtime Flow:
• JavaScript → Mjølner Runtime
• Runtime → Target Process
• Bridge → Native Functions
Technical Details to Highlight
• Parser components (src/Parser.ypp.in, Scanner.lpp.in)
• Bridge system (src/Bridge.*)
• Analysis components (src/Analysis.cpp, Analyze.cpp)
• Multiple language support (ObjectiveC, Java folders)
Notes for Implementation
• Keep the main flow clear and centered
• Related components visually
• Use consistent spacing and alignment
• Version information
• Notes about platform-specific behaviors