@trackunit/i18n-library-translation
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| license | uncommon-license:SEE LICENSE IN LICENSE.txt | AI (license): Custom license file reference; stable across versions of this package. | ai | |
| dependencies | unvetted-dep:i18next-resources-to-backend | AI (dependencies): i18next-resources-to-backend is a standard i18next ecosystem package; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Trackunit org package; provenance absence is consistent across their published packages and not a malware signal. | ai |
Versions (showing 100 of 654)
| Version | Deps | Published |
|---|---|---|
| 1.3.140 | 9 / 0 | |
| 1.3.139 | 9 / 0 | |
| 1.3.138 | 9 / 0 | |
| 1.3.137 | 9 / 0 | |
| 1.3.136 | 9 / 0 | |
| 1.3.135 | 9 / 0 | |
| 1.3.134 | 9 / 0 | |
| 1.3.133 | 9 / 0 | |
| 1.3.132 | 9 / 0 | |
| 1.3.131 | 9 / 0 | |
| 1.3.130 | 9 / 0 | |
| 1.3.128 | 9 / 0 | |
| 1.3.127 | 9 / 0 | |
| 1.3.126 | 9 / 0 | |
| 1.3.124 | 9 / 0 | |
| 1.3.123 | 8 / 0 | |
| 1.3.121 | 8 / 0 | |
| 1.3.120 | 8 / 0 | |
| 1.3.119 | 8 / 0 | |
| 1.3.118 | 8 / 0 | |
| 1.3.117 | 8 / 0 | |
| 1.3.116 | 8 / 0 | |
| 1.3.114 | 8 / 0 | |
| 1.3.112 | 8 / 0 | |
| 1.3.111 | 8 / 0 | |
| 1.3.110 | 8 / 0 | |
| 1.3.109 | 8 / 0 | |
| 1.3.108 | 8 / 0 | |
| 1.3.106 | 8 / 0 | |
| 1.3.105 | 8 / 0 | |
| 1.3.102 | 8 / 0 | |
| 1.3.101 | 8 / 0 | |
| 1.3.100 | 8 / 0 | |
| 1.3.99 | 8 / 0 | |
| 1.3.98 | 8 / 0 | |
| 1.3.96 | 8 / 0 | |
| 1.3.95 | 8 / 0 | |
| 1.3.93 | 8 / 0 | |
| 1.3.92 | 8 / 0 | |
| 1.3.91 | 8 / 0 | |
| 1.3.90 | 8 / 0 | |
| 1.3.89 | 8 / 0 | |
| 1.3.88 | 8 / 0 | |
| 1.3.87 | 8 / 0 | |
| 1.3.85 | 8 / 0 | |
| 1.3.84 | 8 / 0 | |
| 1.3.83 | 8 / 0 | |
| 1.3.82 | 8 / 0 | |
| 1.3.80 | 8 / 0 | |
| 1.3.79 | 8 / 0 | |
| 1.3.78 | 8 / 0 | |
| 1.3.77 | 8 / 0 | |
| 1.3.75 | 8 / 0 | |
| 1.3.74 | 8 / 0 | |
| 1.3.73 | 8 / 0 | |
| 1.3.72 | 8 / 0 | |
| 1.3.70 | 8 / 0 | |
| 1.3.69 | 8 / 0 | |
| 1.3.68 | 8 / 0 | |
| 1.3.66 | 8 / 0 | |
| 1.3.65 | 8 / 0 | |
| 1.3.64 | 8 / 0 | |
| 1.3.63 | 8 / 0 | |
| 1.3.62 | 8 / 0 | |
| 1.3.60 | 8 / 0 | |
| 1.3.59 | 8 / 0 | |
| 1.3.58 | 8 / 0 | |
| 1.3.57 | 8 / 0 | |
| 1.3.56 | 8 / 0 | |
| 1.3.55 | 8 / 0 | |
| 1.3.54 | 8 / 0 | |
| 1.3.53 | 8 / 0 | |
| 1.3.52 | 8 / 0 | |
| 1.3.51 | 8 / 0 | |
| 1.3.50 | 8 / 0 | |
| 1.3.48 | 8 / 0 | |
| 1.3.47 | 8 / 0 | |
| 1.3.45 | 8 / 0 | |
| 1.3.44 | 8 / 0 | |
| 1.3.43 | 8 / 0 | |
| 1.3.42 | 8 / 0 | |
| 1.3.41 | 8 / 0 | |
| 1.3.40 | 8 / 0 | |
| 1.3.38 | 8 / 0 | |
| 1.3.37 | 8 / 0 | |
| 1.3.36 | 8 / 0 | |
| 1.3.35 | 8 / 0 | |
| 1.3.34 | 8 / 0 | |
| 1.3.33 | 8 / 0 | |
| 1.3.31 | 8 / 0 | |
| 1.3.30 | 8 / 0 | |
| 1.3.29 | 8 / 0 | |
| 1.3.28 | 8 / 0 | |
| 1.3.24 | 8 / 0 | |
| 1.3.22 | 8 / 0 | |
| 1.3.21 | 8 / 0 | |
| 1.3.19 | 8 / 0 | |
| 1.3.18 | 8 / 0 | |
| 1.3.17 | 8 / 0 | |
| 1.3.15 | 8 / 0 |
v1.3.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.83
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.82
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.80
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.79
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.78
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.77
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.75
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.74
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.73
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.72
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.64
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.59
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.57
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.55
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.53
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.52
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.50
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.47
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.45
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.43
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.