Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit 02c3d1d

Browse files
authoredJun 22, 2025··
Update readme with some important notes (#150)
1 parent 8378ef6 commit 02c3d1d

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed
 

‎README.md

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,41 @@
11
# Certificate transparency for Android and JVM
22

3+
:warning: While I strive to continue supporting this open-source project, I
4+
don’t always have the time or resources to do so consistently. As a result,
5+
issue resolution may take time.
6+
7+
At the time of writing, the most significant issues are:
8+
9+
1. **Dependency on Chrome’s Log List Files** As previously highlighted by
10+
engineers at Google, this library currently
11+
relies directly on Chrome’s log list files. While this primarily works, it
12+
carries inherent risks due to potential schema changes. Please refer to
13+
[#70](https://github.com/appmattus/certificatetransparency/issues/70)
14+
and [#143](https://github.com/appmattus/certificatetransparency/issues/143)
15+
for additional background information.
16+
17+
I lack the time and resources to host and manage this file independently;
18+
therefore, it’s up to the users of the library to determine the best way to
19+
host and manage the file themselves.
20+
21+
1. **Android 16 (API 36) Support** Support for Android 16 is still in progress.
22+
I do not have access to a
23+
physical device running API 36, and the emulator has proven unreliable. As
24+
such, I’m relying on the community to help find a working solution (see
25+
[#142](https://github.com/appmattus/certificatetransparency/issues/142)).
26+
27+
Given that API 36 finally introduces native support for Certificate
28+
Transparency (after a seven-year wait), the most practical approach might be
29+
to turn off this library on API 36 and utilise the built-in support instead.
30+
31+
1. **Caching Mechanism Issues** There are known problems with the library’s
32+
caching mechanism (see
33+
[#98](https://github.com/appmattus/certificatetransparency/issues/98)). I
34+
want to develop a more robust solution but haven’t yet had the focused time
35+
required to do so.
36+
37+
---
38+
339
[![CI status](https://github.com/appmattus/certificatetransparency/actions/workflows/main.yml/badge.svg)](https://github.com/appmattus/certificatetransparency/actions)
440
[![codecov](https://codecov.io/gh/appmattus/certificatetransparency/branch/main/graph/badge.svg)](https://codecov.io/gh/appmattus/certificatetransparency)
541
[![Maven Central](https://img.shields.io/maven-central/v/com.appmattus.certificatetransparency/certificatetransparency)](https://central.sonatype.com/search?q=com.appmattus.certificatetransparency)

0 commit comments

Comments
 (0)
Please sign in to comment.