You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At long last- this is the first **stable v1** release of Tempel! 🎉
11
+
12
+
It is functionally identical to (and bidirectionally data compatible with) v1.0.0-RC1 (2024-02-26), but now marked as "production ready".
13
+
14
+
## Disclaimer
15
+
16
+
⚠️ **Important**: this software is provided *"as is"* and **without warranty of any kind**. You use it **at your own risk**!
17
+
18
+
While Tempel has been written and tested with care, the nature of the problem domain inevitably means that it can be **easy to misuse** and **sensitive to bugs**.
19
+
20
+
Misuse or bugs can be **especially harmful** - potentially leading to [security vulnerabilities](../../wiki/3-FAQ#how-secure-is-tempel) or even [permanent data loss](../../wiki/3-FAQ#is-there-a-risk-of-data-loss)!
21
+
22
+
Whenever you use cryptographic libraries/frameworks (including Tempel), please **test very carefully** and always **back up important data**!
23
+
24
+
Please report any unexpected issues! Possible security issues may be responsibly reported [here](https://github.com/taoensso/tempel/security), thank you! 🙏
25
+
26
+
## Since `v1.0.0-RC1` (2024-02-26)
27
+
28
+
- Use [contextual Truss exceptions](https://github.com/taoensso/truss#contextual-exceptions) for all errors
29
+
- Documentation and example improvements
30
+
- Update dependencies
31
+
32
+
---
33
+
5
34
# `v1.0.0-RC1` (2024-02-26)
6
35
7
36
> **Dep/s**: Tempel is [on Clojars](https://clojars.org/com.taoensso/tempel/versions/1.0.0-RC1).
Copy file name to clipboardExpand all lines: README.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
<ahref="https://www.taoensso.com/clojure"title="More stuff by @ptaoussanis at www.taoensso.com"><imgsrc="https://www.taoensso.com/open-source.png"alt="Taoensso open source"width="340"/></a>
@@ -14,7 +14,7 @@ More than another collection of crypto utils, Tempel offers a **coherent and opi
14
14
15
15
Its [tiny API](../../wiki/1-Getting-started#api-overview) and focus on **smart keychains** helps shield you from unnecessary and error-prone complexity, greatly simplifying the most common data security needs.
16
16
17
-
⚠️ Tempel is [NOT intended](../../wiki/3-Faq#can-i-decrypt-tempel-data-with-other-tools) for interop with other cryptographic tools/APIs!
17
+
👉 Tempel is [NOT intended](../../wiki/3-Faq#can-i-decrypt-tempel-data-with-other-tools) for interop with other cryptographic tools/APIs!
18
18
19
19
## Why Tempel?
20
20
@@ -83,15 +83,17 @@ See for intro and usage:
83
83
84
84
## Disclaimer
85
85
86
-
**Important**: while Tempel has been written and tested with care, the nature of the problem domain inevitably means that bugs and/or misuse can be **especially harmful and/or easy to make**.
86
+
⚠️ **Important**: this software is provided *"as is"*and **without warranty of any kind**. You use it **at your own risk**!
87
87
88
-
Bugs and/or misuse could lead to [security vulnerabilities](../../wiki/3-FAQ#how-secure-is-tempel) or even [permanent data loss](../../wiki/3-FAQ#is-there-a-risk-of-data-loss).
88
+
While Tempel has been written and tested with care, the nature of the problem domain inevitably means that it can be **easy to misuse** and **sensitive to bugs**.
89
89
90
-
Please be **very careful** evaluating Tempel and/or other cryptographic libraries/frameworks before use, especially new libraries/frameworks like Tempel!
90
+
Misuse or bugs can be **especially harmful** - potentially leading to [security vulnerabilities](../../wiki/3-FAQ#how-secure-is-tempel) or even [permanent data loss](../../wiki/3-FAQ#is-there-a-risk-of-data-loss)!
91
+
92
+
Whenever you use cryptographic libraries/frameworks (including Tempel), please **test very carefully** and always **back up important data**!
91
93
92
94
## Security
93
95
94
-
See [here](../../security) for **security advisories** and/or to **report security vulnerabilities**.
96
+
See [here](../../security) for **security advisories** and/or to **report possible security vulnerabilities**.
0 commit comments