@thi.ng/arrays
Array / Arraylike utilities
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): Established thi.ng/umbrella monorepo package; provenance absence is consistent across all versions. | ai |
Versions (showing 51 of 182)
| Version | Deps | Published |
|---|---|---|
| 2.14.25 | 6 / 3 | |
| 2.14.24 | 6 / 3 | |
| 2.14.23 | 6 / 3 | |
| 2.14.22 | 6 / 3 | |
| 2.14.21 | 6 / 3 | |
| 2.14.19 | 6 / 3 | |
| 2.14.18 | 6 / 3 | |
| 2.14.16 | 6 / 3 | |
| 2.14.15 | 6 / 3 | |
| 2.14.14 | 6 / 3 | |
| 2.14.13 | 6 / 3 | |
| 2.14.12 | 6 / 3 | |
| 2.14.11 | 6 / 3 | |
| 2.14.10 | 6 / 3 | |
| 2.14.9 | 6 / 3 | |
| 2.14.7 | 6 / 3 | |
| 2.14.6 | 6 / 3 | |
| 2.14.5 | 6 / 3 | |
| 2.14.4 | 6 / 3 | |
| 2.14.3 | 6 / 3 | |
| 2.14.2 | 6 / 3 | |
| 2.14.1 | 6 / 3 | |
| 2.14.0 | 6 / 3 | |
| 2.13.16 | 6 / 3 | |
| 2.13.15 | 6 / 3 | |
| 2.13.11 | 6 / 3 | |
| 2.13.10 | 6 / 3 | |
| 2.13.9 | 6 / 3 | |
| 2.13.8 | 6 / 3 | |
| 2.13.7 | 6 / 3 | |
| 2.13.6 | 6 / 3 | |
| 2.13.5 | 6 / 3 | |
| 2.13.4 | 6 / 3 | |
| 2.13.3 | 6 / 3 | |
| 2.13.2 | 6 / 3 | |
| 2.13.1 | 6 / 3 | |
| 2.13.0 | 6 / 3 | |
| 2.12.0 | 6 / 3 | |
| 2.11.2 | 6 / 3 | |
| 2.11.1 | 6 / 3 | |
| 2.11.0 | 6 / 3 | |
| 2.10.23 | 6 / 3 | |
| 2.10.22 | 6 / 3 | |
| 2.10.21 | 6 / 3 | |
| 2.10.20 | 6 / 3 | |
| 2.10.19 | 6 / 3 | |
| 2.10.18 | 6 / 3 | |
| 2.10.17 | 6 / 3 | |
| 2.10.16 | 6 / 3 | |
| 2.10.15 | 6 / 3 | |
| 2.10.14 | 6 / 3 |
v2.14.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.14.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.