@unikue/ts-lang-utils
Common lang utilities for typescript
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): No provenance is common (~88% of npm); no other risk signals present to elevate this. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.2.11 | 5 / 18 | |
| 1.2.10 | 5 / 18 | |
| 1.2.9 | 5 / 18 | |
| 1.2.8 | 5 / 17 | |
| 1.2.7 | 5 / 17 | |
| 1.2.6 | 5 / 17 | |
| 1.2.5 | 5 / 17 | |
| 1.2.4 | 5 / 17 | |
| 1.2.3 | 5 / 17 | |
| 1.2.2 | 5 / 17 | |
| 1.2.1 | 5 / 17 | |
| 1.2.0 | 5 / 17 | |
| 1.1.0 | 5 / 18 | |
| 1.0.0 | 5 / 15 |
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.