@thi.ng/cache
In-memory cache implementations with ES6 Map-like API and different eviction strategies
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): thi.ng/umbrella monorepo does not use Sigstore provenance; consistent across all versions. | ai |
Versions (showing 51 of 208)
| Version | Deps | Published |
|---|---|---|
| 2.3.82 | 2 / 3 | |
| 2.3.81 | 2 / 3 | |
| 2.3.80 | 2 / 3 | |
| 2.3.79 | 2 / 3 | |
| 2.3.78 | 2 / 3 | |
| 2.3.76 | 2 / 3 | |
| 2.3.75 | 2 / 3 | |
| 2.3.73 | 2 / 3 | |
| 2.3.72 | 2 / 3 | |
| 2.3.71 | 2 / 3 | |
| 2.3.70 | 2 / 3 | |
| 2.3.69 | 2 / 3 | |
| 2.3.68 | 2 / 3 | |
| 2.3.67 | 2 / 3 | |
| 2.3.66 | 2 / 3 | |
| 2.3.65 | 2 / 3 | |
| 2.3.63 | 2 / 3 | |
| 2.3.62 | 2 / 3 | |
| 2.3.61 | 2 / 3 | |
| 2.3.60 | 2 / 3 | |
| 2.3.59 | 2 / 3 | |
| 2.3.58 | 2 / 3 | |
| 2.3.57 | 2 / 3 | |
| 2.3.56 | 2 / 3 | |
| 2.3.55 | 2 / 3 | |
| 2.3.54 | 2 / 3 | |
| 2.3.50 | 2 / 3 | |
| 2.3.49 | 2 / 3 | |
| 2.3.48 | 2 / 3 | |
| 2.3.47 | 2 / 3 | |
| 2.3.46 | 2 / 3 | |
| 2.3.45 | 2 / 3 | |
| 2.3.44 | 2 / 3 | |
| 2.3.43 | 2 / 3 | |
| 2.3.42 | 2 / 3 | |
| 2.3.41 | 2 / 3 | |
| 2.3.40 | 2 / 3 | |
| 2.3.39 | 2 / 3 | |
| 2.3.38 | 2 / 3 | |
| 2.3.37 | 2 / 3 | |
| 2.3.36 | 2 / 3 | |
| 2.3.35 | 2 / 3 | |
| 2.3.34 | 2 / 3 | |
| 2.3.33 | 2 / 3 | |
| 2.3.32 | 2 / 3 | |
| 2.3.31 | 2 / 3 | |
| 2.3.30 | 2 / 3 | |
| 2.3.29 | 2 / 3 | |
| 2.3.28 | 2 / 3 | |
| 2.3.27 | 2 / 3 | |
| 2.3.26 | 2 / 3 |
v2.3.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.81
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.