| Key | Value |
|---|---|
| FileName | ./usr/lib/python3.9/site-packages/pylint/extensions/__pycache__/bad_builtin.cpython-39.pyc |
| FileSize | 1937 |
| MD5 | 7420609C46930F2269F75D5CAD0A4B7F |
| SHA-1 | 046924CEFB0544A807BAF704D9151726A1FFC08C |
| SHA-256 | FFE445BC4FF24FED89A2F0465718640870C3694F4609097CE0CF11AFC558FE35 |
| SSDEEP | 48:2RYzUQHF9uzonsKPeNrnjV25kZzt5r3CUmju16zP:w0fF94onsKPepVLn57Pm6wP |
| TLSH | T11A41B76D60096B36F97BF3BDD46F235CE460E0377BE261026A8CD9960F1E488D02761D |
| hashlookup:parent-total | 1 |
| hashlookup:trust | 55 |
The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:
| Key | Value |
|---|---|
| MD5 | DFFBE856BC08D2FA12587193F2C6A4F0 |
| PackageArch | noarch |
| PackageDescription | Pylint analyzes Python source code looking for bugs and signs of poor quality. Pylint is a python tool that checks if a module satisfies a coding standard. Pylint can be seen as another PyChecker since nearly all tests you can do with PyChecker can also be done with Pylint. But Pylint offers some more features, like checking line-code's length, checking if variable names are well-formed according to your coding standard, or checking if declared interfaces are truly implemented, and much more (see the complete check list). The big advantage with Pylint is that it is highly configurable, customizable, and you can easily write a small plugin to add a personal feature. |
| PackageName | python39-pylint |
| PackageRelease | 1.1 |
| PackageVersion | 2.8.3 |
| SHA-1 | 7D20926F070A38F56DAB36BEF42028D0AE21EA5C |
| SHA-256 | C7135276F72CA6D6180EB79508C6A7BD8ED22C314FA820E09935761B459EAA9C |