From 5c735fba9977564912fe41d0cb133ddb2753c220 Mon Sep 17 00:00:00 2001
From: Evan Su <48808396+HACKERALERT@users.noreply.github.com>
Date: Tue, 5 Aug 2025 22:35:18 -0400
Subject: [PATCH] Update README.md: add archival notice
---
README.md | 10 +++++++++-
1 file changed, 9 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
index 375fa02..dcaf953 100644
--- a/README.md
+++ b/README.md
@@ -12,6 +12,14 @@ Picocrypt is a very small (hence Pico), very simple, yet very secure encr

+> # ❄️ Project archived ❄️
+>
+> Picocrypt has been permanently archived and frozen into a read-only state. [Read the explanation](https://github.com/Picocrypt/Picocrypt/issues/134).
+>
+> **Picocrypt is still fully functional, stable, and secure as is. You can continue using it confidently.**
+>
+> Archiving Picocrypt doesn't mean there's anything wrong with it, just that I'm done working on it.
+
# Downloads
ℹ️ **You are highly recommended to read through the [Features](https://github.com/Picocrypt/Picocrypt?tab=readme-ov-file#features) section below to fully understand the features and limitations of Picocrypt before using it.** ℹ️
@@ -162,6 +170,6 @@ Finally, thanks to these people/organizations for helping me out when needed:
@AsuxAX and @Minibus93 for testing new features
@mdanish-kh and @stephengillie for WinGet package
@Retengart for helping create the Flatpak and housekeeping it
- Privacy Guides for listing Picocrypt
+ Privacy Guides for (previously) listing Picocrypt
Radically Open Security for auditing Picocrypt