@djangocfg/debuger
Floating debug panel for DjangoCFG — logs, store inspection, monitor bridge, Cmd+D shortcut
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:debug | AI (typosquat): Scoped @djangocfg package; 'debuger' is a debug panel component, not an impersonation of the 'debug' npm package. | ai |
Versions (showing 76 of 178)
| Version | Deps | Published |
|---|---|---|
| 2.1.309 | 0 / 8 | |
| 2.1.308 | 0 / 8 | |
| 2.1.307 | 0 / 8 | |
| 2.1.304 | 0 / 8 | |
| 2.1.303 | 0 / 8 | |
| 2.1.302 | 0 / 8 | |
| 2.1.301 | 0 / 8 | |
| 2.1.300 | 0 / 8 | |
| 2.1.299 | 0 / 8 | |
| 2.1.298 | 0 / 8 | |
| 2.1.297 | 0 / 8 | |
| 2.1.294 | 0 / 8 | |
| 2.1.293 | 0 / 8 | |
| 2.1.292 | 0 / 8 | |
| 2.1.291 | 0 / 8 | |
| 2.1.290 | 0 / 8 | |
| 2.1.289 | 0 / 8 | |
| 2.1.287 | 0 / 8 | |
| 2.1.286 | 0 / 8 | |
| 2.1.285 | 0 / 8 | |
| 2.1.284 | 0 / 8 | |
| 2.1.283 | 0 / 8 | |
| 2.1.282 | 0 / 8 | |
| 2.1.281 | 0 / 8 | |
| 2.1.280 | 0 / 8 | |
| 2.1.279 | 0 / 8 | |
| 2.1.277 | 0 / 8 | |
| 2.1.276 | 0 / 8 | |
| 2.1.275 | 0 / 8 | |
| 2.1.274 | 0 / 8 | |
| 2.1.272 | 0 / 8 | |
| 2.1.271 | 0 / 8 | |
| 2.1.270 | 0 / 8 | |
| 2.1.268 | 0 / 8 | |
| 2.1.267 | 0 / 8 | |
| 2.1.266 | 0 / 8 | |
| 2.1.264 | 0 / 8 | |
| 2.1.263 | 0 / 8 | |
| 2.1.262 | 0 / 8 | |
| 2.1.261 | 0 / 8 | |
| 2.1.260 | 0 / 8 | |
| 2.1.259 | 0 / 8 | |
| 2.1.257 | 0 / 8 | |
| 2.1.256 | 0 / 8 | |
| 2.1.255 | 0 / 8 | |
| 2.1.254 | 0 / 8 | |
| 2.1.252 | 0 / 8 | |
| 2.1.251 | 0 / 8 | |
| 2.1.249 | 0 / 8 | |
| 2.1.248 | 0 / 8 | |
| 2.1.247 | 0 / 8 | |
| 2.1.246 | 0 / 8 | |
| 2.1.243 | 0 / 8 | |
| 2.1.242 | 0 / 8 | |
| 2.1.241 | 0 / 8 | |
| 2.1.240 | 0 / 8 | |
| 2.1.239 | 0 / 8 | |
| 2.1.238 | 0 / 8 | |
| 2.1.237 | 0 / 8 | |
| 2.1.236 | 0 / 8 | |
| 2.1.235 | 0 / 8 | |
| 2.1.234 | 0 / 8 | |
| 2.1.233 | 0 / 8 | |
| 2.1.232 | 0 / 8 | |
| 2.1.231 | 0 / 8 | |
| 2.1.230 | 0 / 8 | |
| 2.1.229 | 0 / 8 | |
| 2.1.228 | 0 / 8 | |
| 2.1.227 | 0 / 8 | |
| 2.1.226 | 0 / 8 | |
| 2.1.225 | 0 / 8 | |
| 2.1.224 | 0 / 8 | |
| 2.1.223 | 0 / 8 | |
| 2.1.222 | 0 / 8 | |
| 2.1.221 | 0 / 8 | |
| 2.1.219 | 0 / 8 |
v2.1.304
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.301
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.275
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.274
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.272
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.271
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.270
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.268
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.267
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.266
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.264
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.263
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.262
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.261
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.260
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.257
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.256
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.252
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.251
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.248
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.247
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.242
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.241
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.240
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.239
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.238
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.237
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.236
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.235
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.234
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.233
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.232
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.231
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.230
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.229
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.228
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.227
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.226
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.225
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.224
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.223
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.222
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.221
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.219
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.