Welcome to DucklingScript, a language that compiles into Rubber Ducky Scripting Language 1.0! DucklingScript is the best language to use for BadUSB on the Flipper Zero. Although this is the main idea, there are many other applications as well!
All documentation, contributing guides, are found here!
Issues and PR's are welcome!
Documentation
We got you covered! Docs are hosted on a separate website found here!
VSCode Support
DucklingScript has a public VSCode extension that supports syntax highlighting.
DucklingScript VSCode Extension ->
Why DucklingScript?
There are many key points to using DucklingScript, such as Type Safety, Flow Control, Syntactical Speed, and Forward Compatibility.
Type Safety
Because DucklingScript has to go through a compilation process, it means DucklingScript can validate your script will work on your hardware. It will tell you that there is an error, and it will tell you exactly where. For example, CTRL requires one character. DucklingScript will validate that this is true.
Flow Control
Rubber Ducky Scripting Language 1.0 and even the Flipper's implementation don't add any kind of flow control. e.g. if statements, while/for loops, etc. DucklingScript gives you those capabilities, and more!
Syntactical Speed
Normal Rubber Ducky Scripting 1.0 doesn't give much room for speed, and oftentimes leads you to repeating yourself in code. Not only does DucklingScript add commands to improve this, it also makes small syntactical changes. Such as:
Rubber Ducky 1.0
STRINGLN Hello,
STRINGLN world,
STRINGLN it is I!
DucklingScript
STRINGLN
Hello,
world,
it is I!
Forward Compatibility
If you use a command that does not exist in Rubber Ducky 1.0, DucklingScript will simply warn you that this is the case (these warnings can even be supressed using a flag on compilation, or editing the config file). However, it does not stop you from doing so. This allows you to use future commands!
Support Me 💖
If you'd like to support me or this project, you can support me through my Ko-Fi: https://ko-fi.com/dragonofshuu.
1 maintainer
Metadata
1 maintainer
Release files for ducklingscript 0.2.3
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 | |
|---|---|---|---|---|
| ducklingscript-0.2.3.tar.gz | 48.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ducklingscript-0.2.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 138.0 kB
Release files / ducklingscript-0.2.3.tar.gz
| Download URL | ducklingscript-0.2.3.tar.gz |
|---|---|
| Size | 48.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bbe550de4fcc78363834b57ea5c388cffc97f554b4f0b9094140e08e92d43661
|
|
BLAKE2b-256 checksum How to use checksums |
6966d390f8537f1e5cca2fd2bf33dbc789256bbb43fecafc5644b26bab5d8c4d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.11.9 Windows/10
|
Release files / ducklingscript-0.2.3-py3-none-any.whl
| Download URL | ducklingscript-0.2.3-py3-none-any.whl |
|---|---|
| Size | 89.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
75e8bed27d6af9da78f4e8fb2ef6b4355dd6890fa96ddde47ba57214a5523c51
|
|
BLAKE2b-256 checksum How to use checksums |
d2051d36572f9100459c750ed592157ff97e2750bf8dfa3a7dd00527b4e6faa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/2.1.3 CPython/3.11.9 Windows/10
|
Security for ducklingscript 0.2.3
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.
