Frequently Asked Questions

🤔 Why is my antivirus (like Windows Defender) flagging Chronicler?

You might see a warning from Windows Defender or other antivirus software identifying Chronicler with a generic threat name like "Trojan:Script/Wacatac.B!ml" or similar. Please be reassured: this is a false positive, and Chronicler is safe to use.

This happens because modern antivirus programs use machine learning to detect potential threats by looking for suspicious patterns. As a new application from an independent developer, Chronicler exhibits a combination of behaviors that can, unfortunately, trigger these algorithms:

• Unsigned Application: The primary reason for the flag is that Chronicler is not "code-signed." Code signing certificates are used to verify a developer's identity, but they are very expensive (often hundreds of dollars per year). This cost is prohibitive for a small, community-funded project like this one. Unsigned apps are treated with extra suspicion by default.
• Internet Connection: Chronicler connects to the internet for one reason only: to check for new versions so it can auto-update. An algorithm sees an unknown, unsigned app making web requests and can flag it as suspicious.
• File System Access: The entire purpose of Chronicler is to create, read, and write local files (`.md` notes) in a folder you choose (your "vault"). This is a necessary function, but it's also a behavior that antivirus software monitors closely.

Transparency and Security

I believe in full transparency, which is why Chronicler is source-available. You can view the entire codebase on my GitHub repository to see for yourself exactly what the application does.

Furthermore, while the initial installer is unsigned, it is crucial to know that all in-app auto-updates are cryptographically signed. Chronicler uses Tauri's secure built-in updater, which automatically verifies the signature of every update before installing it. This ensures that once installed, any future versions you receive are authentic and have not been tampered with.

You can safely bypass the Windows warning by clicking "More info" and then "Run anyway". Thank you for your trust and for supporting independent software.