Installation

Mojic is distributed via NPM. You can install it globally to use the command line tools.

Global Install

npm install -g mojicCopy

Run via NPX (No Install)

npx mojic --helpCopy

Build from Source

git clone https://github.com/notamitgamer/mojic.git
cd mojic
npm install
npm run build-binariesCopy

mojic encode

Encrypts a C source file or an entire directory of files into Mojic format.

Usage

mojic encode <path> [options]

Options

Examples

Encrypt a single file:

$ mojic encode main.c
> Create password for file(s): *****
> Processing: main.c -> main.mojic
> Encrypted.Copy

Batch encrypt a project with flattening:

$ mojic encode ./src -r -f
> Initiating Mojic Encryption v2.1...
> Structural Flattening Enabled
> Scanning directory: ./src
> Processing: utils.c -> utils.mojic
> Processing: main.c -> main.mojic
> Batch encryption complete.Copy

mojic decode

Restores .mojic files back to readable C source code.

Usage

mojic decode <path> [options]

Options

Error Handling

Mojic includes strict integrity checks.

• WRONG_PASSWORD: The derived key did not match the Auth Check in the Moon Header.
• FILE_TAMPERED: The HMAC-SHA256 signature at the end of the stream failed. The file has been modified.

Security & Rotation Tools (SRT)

The srt command allows you to manage encrypted files without exposing their plaintext contents. This is useful for rotating credentials.

Rotate Password

Changes the password of a file by decrypting the stream into memory and re-encrypting with a new key.

mojic srt --pass secret.mojicCopy

Re-Encrypt (Entropy Shuffle)

Keeps the same password but generates a new salt and AES keystream. This completely changes the visual emoji output, defeating any potential pattern analysis over time.

mojic srt --re secret.mojicCopy

Operation Ironclad (v2.1.4)

Mojic is built on the updated CipherEngine.js. Here is how it achieves "Polymorphic Chaos".

1. The Emoji Universe

The engine generates a pool of ~1,100 valid unicode characters (Emoticons, Transport, Symbols). This pool is shuffled using a CSPRNG (AES-256-CTR) seeded by your password.

2. Polymorphic Keywords

Standard C keywords (int, void, if) are not mapped 1:1. The engine calculates a random offset for every occurrence based on the keystream.

3. XOR Whitening

Before any raw data (variable names, strings, whitespace) is encoded, it is XORed with a mask generated from the AES-256-CTR stream. This ensures that repeating patterns—like 4 spaces of indentation—never look the same twice.

4. Base-1024 Compression

The whitened data is buffered into 5-byte chunks and converted into 4 base-1024 digits (emojis), keeping file sizes manageable.

Moon Header Protocol

Mojic files do not look like random noise immediately. They start with a distinct header.

Structure

The header contains the Salt (32 bytes) and an Auth Check (4 bytes). These are encoded using a specific alphabet of moon phases and clocks.

HEADER_ALPHABET = ['🌑', '🌒', '🌓', '🌔', '🌕', '🌖', '🌗', '🌘', '🕐', '🕑', '🕒', '🕓', '🕔', '🕕', '🕖', '🕗'];

This allows the decode command to verify your password instantly by checking the header, rather than processing the whole file and outputting garbage.

Contributing to Mojic

First off, thanks for taking the time to contribute! Use your best judgment, and feel free to propose changes.

Development Workflow

1. Fork the repository on GitHub.
2. Clone your fork locally: git clone https://github.com/YOUR_USERNAME/mojic.git
3. Create a Branch for your feature or bugfix: git checkout -b feature/amazing-feature
4. Install Dependencies: npm install
5. Test your changes: Run the CLI locally using npm start -- encode test.c
6. Commit your changes using imperative mood (e.g., "Add feature").
7. Push and Open a Pull Request.

Mojic Code Style

• Cipher Logic: Changes to CipherEngine.js must ensure backward compatibility.
• Streams: Always use StringDecoder when handling text streams to prevent multi-byte emoji corruption.

Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team. All complaints will be reviewed and investigated.

Security Policy

Reporting a Vulnerability

We take security seriously. If you discover a security vulnerability within Mojic (e.g., in the CipherEngine logic or the PRNG implementation), please send an e-mail immediately.

Scope

• Supported: Issues regarding key derivation (Scrypt), salt collisions, HMAC integrity failures, or stream buffer overflows.
• Not Supported: Brute-forcing weak passwords (users are responsible for password strength).

License

Mojic is licensed under the Apache License, Version 2.0.

Copyright © 2026 notamitgamer