Skip to main content

applescript-decompiler

Decompiler for compiled AppleScript (.scpt) files. Parses the Fasd UAS binary format and reconstructs readable AppleScript source from the bytecode — including handlers, control flow (if/repeat/try/tell blocks), object specifiers, and literals.

Built on (and a significant extension of) Jinmo/applescript-disassembler.

Installation

pip install applescript-decompiler

Or from a checkout:

pip install .

Requires Python 3.11+.

Usage

Command line

asdec compiled.scpt
========================================
Function: areaOfCircle
Arguments: none
========================================
if (not ({real, integer} contains class of var_0)) then
    error "Radius must be number."
else
end if
return ((var_0 * var_0) * |«class pi  »|)

As a library

from applescript_decompiler import decompile_file

source = decompile_file("compiled.scpt")
print(source)

How it works

  • applescript_decompiler.fas parses the Fasd UAS serialization format (a port of the FasLoad routine from the original AppleScript runtime): reference tables, value blocks, records, literals, and embedded bytecode.
  • applescript_decompiler.opcodes knows the 256-entry instruction set and disassembles handler bytecode.
  • applescript_decompiler.decompiler interprets each handler's instructions against a simulated value stack, emitting AppleScript statements as it goes.

Limitations

Decompilation reconstructs source from bytecode, and some information is discarded at compile time or only meaningful with an application's terminology dictionary. Expect:

  • Local variable names are not stored in compiled scripts, so they appear as var_0, var_1, … Handler argument names (including typed and destructuring patterns), globals, and properties are recovered.
  • Labeled parameters of application/scripting-addition commands are not reconstructed. A command's name is recovered (e.g. make, display dialog), but its arguments are rendered positionally rather than with their with properties / given labels.
  • use statements, property initializers, and script object structure (inheritance, nesting) are not reconstructed; only the handlers they contain are emitted.
  • Output is per-handler, framed with =/Function:/Arguments: headers, not a single recompilable file. The handler bodies are valid AppleScript for most inputs; pathological scripts can still leave a stray marker.

A trailing return of the last expression is emitted for every handler (the compiler stores it as the result), which is harmless but not always present in the original.

Development

uv sync          # install dev dependencies
uv run pytest    # run the test suite

The test suite compiles a corpus of AppleScript sources with osacompile (macOS only) and verifies that decompilation round-trips: output must contain no unknown markers, balance its blocks, recompile cleanly, and leave no opcode unhandled.

License

MIT — see LICENSE. Original disassembler © 2017 Jinmo; decompiler extension © 2026 n0kovo.

Metadata

Release files for applescript-decompiler 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for applescript-decompiler 1.0.0
File Size Uploaded
applescript_decompiler-1.0.0.tar.gz 42.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for applescript-decompiler 1.0.0
File Interpreter ABI Platform
applescript_decompiler-1.0.0-py3-none-any.whl Python 3 none any Details

Total release size: 68.2 kB

Release files / applescript_decompiler-1.0.0.tar.gz

Download URL applescript_decompiler-1.0.0.tar.gz
Size 42.9 kB
Tags Source
SHA-256 checksum
How to use checksums
53139e15beee6395c8746bb16ef21a536471661e838d0c265b2615dad9096ade
BLAKE2b-256 checksum
How to use checksums
ddef1102dbc818c15e3c1ccfc49288dfb062671221f6514433db7463f6998b6f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 7, 2026.

Transparency log

Release files / applescript_decompiler-1.0.0-py3-none-any.whl

Download URL applescript_decompiler-1.0.0-py3-none-any.whl
Size 25.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3623588dc5702076f7d01bd7801ea61d0ba550f42e6e5cdee5d1e11c9e2728c7
BLAKE2b-256 checksum
How to use checksums
0cd9057d7fc6f93b82cb212f698da0a0fbdd732779187430a0453387730652d4
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.12

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.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jun 7, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.0.0 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page