@thi.ng/dcons
Double-linked lists with comprehensive set of operations (incl. optional self-organizing behaviors)
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped @thi.ng package in a large monorepo; Levenshtein match to 'cors' is spurious. | ai | |
| dependencies | unvetted-dep:@thi.ng/api | AI (dependencies): Sibling package in the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/random | AI (dependencies): Sibling package in the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/compare | AI (dependencies): Sibling package in the same thi.ng/umbrella monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@thi.ng/transducers | AI (dependencies): Sibling package in the same thi.ng/umbrella monorepo; stable false positive. | ai |
Versions (showing 100 of 208)
| Version | Deps | Published |
|---|---|---|
| 3.2.201 | 7 / 3 | |
| 3.2.200 | 7 / 3 | |
| 3.2.199 | 7 / 3 | |
| 3.2.198 | 7 / 3 | |
| 3.2.197 | 7 / 3 | |
| 3.2.195 | 7 / 3 | |
| 3.2.194 | 7 / 3 | |
| 3.2.192 | 7 / 3 | |
| 3.2.191 | 7 / 3 | |
| 3.2.190 | 7 / 3 | |
| 3.2.189 | 7 / 3 | |
| 3.2.188 | 7 / 3 | |
| 3.2.187 | 7 / 3 | |
| 3.2.186 | 7 / 3 | |
| 3.2.185 | 7 / 3 | |
| 3.2.184 | 7 / 3 | |
| 3.2.182 | 7 / 3 | |
| 3.2.181 | 7 / 3 | |
| 3.2.180 | 7 / 3 | |
| 3.2.179 | 7 / 3 | |
| 3.2.178 | 7 / 3 | |
| 3.2.177 | 7 / 3 | |
| 3.2.176 | 7 / 3 | |
| 3.2.175 | 7 / 3 | |
| 3.2.174 | 7 / 3 | |
| 3.2.173 | 7 / 3 | |
| 3.2.169 | 7 / 3 | |
| 3.2.168 | 7 / 3 | |
| 3.2.167 | 7 / 3 | |
| 3.2.166 | 7 / 3 | |
| 3.2.165 | 7 / 3 | |
| 3.2.164 | 7 / 3 | |
| 3.2.163 | 7 / 3 | |
| 3.2.162 | 7 / 3 | |
| 3.2.161 | 7 / 3 | |
| 3.2.160 | 7 / 3 | |
| 3.2.159 | 7 / 3 | |
| 3.2.158 | 7 / 3 | |
| 3.2.157 | 7 / 3 | |
| 3.2.156 | 7 / 3 | |
| 3.2.155 | 7 / 3 | |
| 3.2.154 | 7 / 3 | |
| 3.2.153 | 7 / 3 | |
| 3.2.152 | 7 / 3 | |
| 3.2.151 | 7 / 3 | |
| 3.2.150 | 7 / 3 | |
| 3.2.149 | 7 / 3 | |
| 3.2.148 | 7 / 3 | |
| 3.2.147 | 7 / 3 | |
| 3.2.146 | 7 / 3 | |
| 3.2.145 | 7 / 3 | |
| 3.2.144 | 7 / 3 | |
| 3.2.143 | 7 / 3 | |
| 3.2.142 | 7 / 3 | |
| 3.2.141 | 7 / 3 | |
| 3.2.140 | 7 / 3 | |
| 3.2.139 | 7 / 4 | |
| 3.2.138 | 7 / 4 | |
| 3.2.137 | 7 / 4 | |
| 3.2.136 | 7 / 4 | |
| 3.2.135 | 7 / 4 | |
| 3.2.134 | 7 / 4 | |
| 3.2.133 | 7 / 4 | |
| 3.2.132 | 7 / 4 | |
| 3.2.131 | 7 / 4 | |
| 3.2.130 | 7 / 4 | |
| 3.2.129 | 7 / 4 | |
| 3.2.128 | 7 / 4 | |
| 3.2.127 | 7 / 4 | |
| 3.2.126 | 7 / 4 | |
| 3.2.125 | 7 / 4 | |
| 3.2.124 | 7 / 4 | |
| 3.2.123 | 7 / 4 | |
| 3.2.122 | 7 / 4 | |
| 3.2.121 | 7 / 4 | |
| 3.2.120 | 7 / 4 | |
| 3.2.119 | 7 / 4 | |
| 3.2.118 | 7 / 4 | |
| 3.2.117 | 7 / 4 | |
| 3.2.116 | 7 / 4 | |
| 3.2.115 | 7 / 4 | |
| 3.2.114 | 7 / 4 | |
| 3.2.113 | 7 / 4 | |
| 3.2.112 | 7 / 4 | |
| 3.2.111 | 7 / 4 | |
| 3.2.110 | 7 / 5 | |
| 3.2.109 | 7 / 5 | |
| 3.2.108 | 7 / 5 | |
| 3.2.107 | 7 / 5 | |
| 3.2.106 | 7 / 5 | |
| 3.2.105 | 7 / 5 | |
| 3.2.104 | 7 / 5 | |
| 3.2.103 | 7 / 5 | |
| 3.2.102 | 7 / 5 | |
| 3.2.101 | 7 / 5 | |
| 3.2.100 | 7 / 5 | |
| 3.2.99 | 7 / 5 | |
| 3.2.98 | 7 / 5 | |
| 3.2.97 | 7 / 5 | |
| 3.2.96 | 7 / 5 |
v3.2.201
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.200
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.150
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.149
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.148
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.147
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.146
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.145
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.144
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.143
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.142
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.141
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.140
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.139
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.138
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.137
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.136
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.135
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.134
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.133
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.132
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.131
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.130
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.129
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.128
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.127
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.126
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.125
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.124
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.123
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.122
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.121
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.115
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.114
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.104
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.100
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.