GitXplorerGitXplorer
t

old-pypi-projects-json

public
4 stars
4 forks
0 issues

Commits

List of commits on branch main.
Unverified
8ec211a18e628bd4d9ce1f814ebb5dde1692d2d6

Remove package-sample by request

tthatch committed 3 years ago
Unverified
b7af56b0c428b31ef6a5b0f80234290236a458f9

Remove enos-mqtt-python-sdk by request.

tthatch committed 3 years ago
Unverified
d6c30c71719312f7afd23fba8b8b0d7268027b1e

Remove edf-pystore

tthatch committed 3 years ago
Unverified
bca52fab44f03ed7e6f252b5a96a694876e01ca2

Remove zkh360nlp by request.

tthatch committed 4 years ago
Unverified
6d3038c93349591e609c0dd76bb7ab50d76c94d8

Add historical deletions

tthatch committed 4 years ago
Verified
3b37ac82c4236949b322b4c4b167e6b762dfe9f3

Initial commit

tthatch committed 4 years ago

README

The README file for this repository.

Old PyPI Projects JSON

In the process of identifying which removed projects are malicious, it's helpful to have more training data. This data comes from a long-running bandersnatch instance, and is prettyprinted, but provides a historical view with last upload dates between 2017-09-15 and 2020-02-16.

The only modification I have made is canonicalizing the filenames (you can get back the original name from the .info.name in the file).

This will eventually be merged with what's available in drd for a more complete view of what was previously on pypi.

license

Short answer: I chose CC0

Longer answer:

I am not a lawyer. This metadata was originally provided to aid distribution, and publicly available, but metadata isn't specifically called out as a use in the pypi ToU.

I am happy to exclude individual projects if you object via github issue here.