VeilCord.
> Custom Discord Tools Going To Be Used For My Projects
And Available To Anyone Else Who Wants To Use <
Installation
pip install veilcord
Example Usages
from veilcord import VeilCord
veilcord = VeilCord(
session = ..., # for custom tls_client sessions
device_type = "browser", # types : browser, mobile, app (aka desktop)
user_agent = ... # for custom user agent
)
# GETTING X-Super-Properties
xsup = veilcord.generateXProp()
print(f"(+) Retrieved XSup: {xsup}")
# GETTING ALL THE COOKIES AND FINGERPRINT
fp, cookies = veilcord.getFingerprint(
xsup,
withCookies = True, # true or false -- will return cookies that are returned in the expirements req
cookieType = "json" # if withCookies is true this can be either "json" or "cookiejar" -- by default its cookiejar
)
print(f"(+) Retrieved Fingerprint: {fp}")
print(f"(+) Retrieved Cookies: {cookies}")
# returns a tuple. [0] - Fingerprint | [1] - COOKIESJAR or JSON
# GET THE NEW SESSION ID BS
_, sessionID = veilcord.getSession(
token = "",
)
if sessionID == "invalid token":
print("invalid token :(")
else:
print(f"(+) Got Session ID: {sessionID}")
## Getting Discord build number
buildNum = VeilCord.getBuildNum()
print(buildNum)
Custom Sessions
session = veilcord.openSession(
custom_rpc = {
"status": "online",
"since": 0,
"activities": [{
"name": "Custom Status",
"type": 4,
"state": "vast#1337",
"emoji": ""
}],
"afk": False
}
)
veilcord.getSession(
token = "", # obv the token
session = session, # the session returned from veilcord.openSession() (if u are using keepAlive)
keep_alive = True, # keep the session alive until closed with veilcord.closeSession()
show_hb = True # prints when it sends the heartbeat and when the next one is
)
# close the session, if keepAlive is enabled.
veilcord.closeSession(session)
> imvast@discord | imvast@github | vast.sh <
Metadata
Release files for veilcord 0.0.7.5
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 | Actions |
|---|---|---|---|---|
| veilcord-0.0.7.5.tar.gz | 17.1 kB | Without provenance | Details for veilcord-0.0.7.5.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| veilcord-0.0.7.5-py3-none-any.whl | Python 3 | none | any | Details for veilcord-0.0.7.5-py3-none-any.whl |
Total release size: 35.3 kB
Release files / veilcord-0.0.7.5.tar.gz
| Download URL | veilcord-0.0.7.5.tar.gz |
|---|---|
| Size | 17.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a4e8850660c7782df0b2d22ec87b88419899d30839fc80d488f2dc4563656f29
|
|
BLAKE2b-256 checksum How to use checksums |
d511eaa73a5c58c0807b17605736cd0a9090e51a979932dd8c7a30243e600005
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Release files / veilcord-0.0.7.5-py3-none-any.whl
| Download URL | veilcord-0.0.7.5-py3-none-any.whl |
|---|---|
| Size | 18.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3451b59e19fe11c5f762e9a84012dc40cf7dd7bee91c5cb600d9fa75861e96ff
|
|
BLAKE2b-256 checksum How to use checksums |
7f1cb0417d1fadf47c7c2361c203ef0cb30168822c1917bd5df2051d6ae5e326
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.5
|
Security for veilcord 0.0.7.5
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.