Greasyfork User Archive
Scrape data from a users Greasyfork account.
For a given user, for each installable script that users created, scrapes:
script name
script authors
daily installs
total installs
rating score
created date
updated date
script type
script version
sensitive
language
css available as js
description
url
code (the script contents)
This does not scrape the script code for items that can't be installed directly, e.g. this
Example
greasyfork_archive 106222 --output-file scraped_data.json
Installation
To install with pip, run:
pip3 install --user greasyfork_archive
Run
Usage: greasyfork_archive [OPTIONS] GREASYFORK_USER_ID
Options:
--output-file PATH JSON filepath to output scraped data to [required]
--help Show this message and exit.
Tests
pip3 install --user pytest vcrpy
pytest
Metadata
Release files for greasyfork-archive 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| greasyfork_archive-0.1.0.tar.gz | 4.8 kB | Without provenance | Details |
Release files / greasyfork_archive-0.1.0.tar.gz
| Download URL | greasyfork_archive-0.1.0.tar.gz |
|---|---|
| Size | 4.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3e8b2f9c174ada0c43bf6b2a92d847cc09f701e01c12754c1516db6b415385da
|
|
BLAKE2b-256 checksum How to use checksums |
baa0e4bdc726544325c554572c9277e29030a4d4a228f5128adfb0989fc388e2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.43.0 CPython/3.8.1
|
Security for greasyfork-archive 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.