Console

Settings

Sign out

Notifications

Alexa

Amazon Appstore

AWS

Documentation

Support

My Cases

Console

Vega Developer Docs

Home

Get Started

Design and Develop

Publish

Reference

Support

Use VPT for Vega App Packages

Open Beta Documentation Amazon offers this technical documentation as part of a pre-release, open beta. The features described might change as Amazon receives feedback and iterates on the features. For the most current feature information, see the Release Notes.

VPT manages Vega app packages. Use it to create, examine, manage, and validate .vpkg files (Vega's standard package format).

To get started with VPT, install the Vega Software Development Kit (SDK), which includes two main command-line tools:

VPT - Manages package operations like creation and validation
Vega CLI - Handles the overall app development workflow, including building and deploying apps

While Vega CLI uses VPT during app builds, you can also run VPT directly to:

Examine packages
Validate content
Add custom signatures to your apps

Commands

VPT provides the following command categories. For a complete list of commands and their latest options, use vega exec vpt --help.

Package information

These commands view package details and contents.

info

Shows package information, including ID, title, and build details.

Copied to clipboard.

Usage: vega exec vpt info [OPTIONS] <PACKAGE>

Arguments:
<PACKAGE>          Path to the vpkg

Options:
  --json           Output in JSON format
  -h, --help       Print help

Example:

vega exec vpt info /path/to/sampleapp.vpkg

// Output
Sample App    com.amazondeveloper.sampleapp v1.3.4 b53

show-contents

Lists all files in the package.

Copied to clipboard.

Usage: vega exec vpt show-contents [OPTIONS] <PACKAGE>

Arguments:
  <PACKAGE>     Path to the vpkg

Options:
  -h, --help    Print help

Example:

vega exec vpt show-contents /path/to/ampleapp.vpkg

// Output
Package contents:
assets/ (6 files)
lib/ (2 files)
manifest.toml
meta-info/ (4 files)

Package creation and extraction

These commands create and modify packages.

pack

Creates a package from source directories. You can specify package name, version, and build number.

Copied to clipboard.

Usage: vega exec vpt pack [OPTIONS] <SOURCE_PATHS>...

Arguments:
  <SOURCE_PATHS>...  Source directories

Options:
  -n, --pkg-name <PKG_NAME>          Name of the package
  -d, --dest-path <DEST_PATH>        Destination path
  -b, --build-number <BUILD_NUMBER>  Build number
  -v, --version <VERSION>            Build version
      --validate                     Enforce validation of the manifest
      --no-strict-abi-check          Disable strict ABI check
  -h, --help                         Print help

Example:

vega exec vpt pack /path/to/source --pkg-name sampleapp --dest-path /path/to/output --version 1.0.0 --build-number 42

// Output
Creating package sampleapp...
Validating manifest...
Package created at /path/to/output/sampleapp.vpkg

unpack

Extracts all package files to a destination path.

Warning: This command overwrites existing files at the destination path without confirmation.

Copied to clipboard.

Usage: vega exec vpt unpack [OPTIONS] <PACKAGE>

Arguments:
  <PACKAGE>                    Path to the vpkg

Options:
  -d, --dest-path <DEST_PATH>  Destination path
  -h, --help                   Print help

Example:

vega exec vpt unpack /path/to/sampleapp.vpkg --dest-path /path/to/output

// Output
Extracting package contents...
Files extracted to /path/to/output

dump

Extracts a file from the package. Prints to stdout, or saves to the destination path you specified.

Warning: This command overwrites files at the destination path without confirmation. Binary files sent to stdout may corrupt your terminal display.

Copied to clipboard.

Usage: vega exec vpt dump [OPTIONS] <PACKAGE> <ENTRY>

Arguments:
  <PACKAGE>                    Path to the vpkg
  <ENTRY>                      Path to the entry inside vpkg

Options:
  -d, --dest-path <DEST_PATH>  Destination path
  -h, --help                   Print help

Example:

vega exec vpt dump /path/to/sampleapp.vpkg manifest.toml

// Output
Extracting manifest.toml from sampleapp.vpkg
Content written to stdout

extract-locales

Extracts localization files from a package as JSON or text.

Copied to clipboard.

Usage: vega exec vpt extract-locales [OPTIONS] <PACKAGE>

Arguments:
  <PACKAGE>                           Path to the vpkg

Options:
  -f, --format <FORMAT>               Output format [default: json] [possible values: json, text]
  -h, --help                          Print help

Example:

vega exec vpt extract-locales --format json /path/to/sampleapp.vpkg

// Output
Extracting localization files...
Files extracted to current directory:
- en/strings.json
- es/strings.json

Package signature and verification

These commands handle security and validation.

pull

Extracts digest and signature files from the package. A digest file lists cryptographic checksums for all files in the VPKG, while a signature file contains a detached cryptographic signature that verifies the digest file's authenticity. Use --json-digest to extract the digest file in JSON format, or --json-signature to extract the signature file in JSON format.

Copied to clipboard.

Usage: vega exec vpt pull [OPTIONS] <--signature|--digest|--json-signature|--json-digest> <PACKAGE> <DEST>

Arguments:
  <PACKAGE>           Path to the vpkg
  <DEST>              Destination path

Options:
  --signature
  --digest
  --json-signature
  --json-digest
  -h, --help          Print help

Example:

vega exec vpt pull --signature /path/to/sampleapp.vpkg /path/to/output/digest.sig

// Output
Extracting signature from sampleapp.vpkg
Signature saved to /path/to/output/digest.sig

push

Adds a signature file to the package. Use --json-signature to insert a JSON-formatted signature file that corresponds to the package's digest.

Copied to clipboard.

Usage: vega exec vpt push [OPTIONS] <--signature <SIGNATURE>|--json-signature <JSON_SIGNATURE>> <PACKAGE>

Arguments:
  <PACKAGE>                           Path to the vpkg

Options:
  --signature <SIGNATURE>             Legacy signature of a digest file path to push
  --json-signature <JSON_SIGNATURE>   Signature of a digest.json file path to push
  -h, --help                          Print help

Example:

vega exec vpt push --signature /path/to/input/digest.sig /path/to/sampleapp.vpkg

// Output
Adding signature to sampleapp.vpkg
Signature successfully added

sign

Signs a message using a private key and certificate.

Copied to clipboard.

Usage: vega exec vpt sign [OPTIONS] <MESSAGE> <PRIVKEY> <CERTFILE> <OUTPUTFILE>

Arguments:
  <MESSAGE>      Message to sign
  <PRIVKEY>      Private key used to sign the message
  <CERTFILE>     X.509 certificate that corresponds to the private key
  <OUTPUTFILE>   Output path

Options:
  -r, --resign   Resign a signed message
  -h, --help     Print help

Example:

vega exec vpt sign --resign /path/to/input/digest.sig /path/to/developer-private.key /path/to/developer-cert.pem /path/to/output/digest.sig

// Output
Signing digest.sig with provided key and certificate
Signature created at /path/to/output/digest.sig

verify

Verifies a message's signature using specified certificates.

Copied to clipboard.

Usage: vega exec vpt verify [OPTIONS] <MESSAGEFILE> <SIGFILE> <CERTIFICATES>...

Arguments:
  <MESSAGEFILE>      File to verify
  <SIGFILE>          Signature used to verify the message
  <CERTIFICATES>...  List of X.509 certificates to verify against

Options:
  -p, --partial      Perform a partial/non-exhaustive verification using only the provided CAs
  -h, --help         Print help

Example:

vega exec vpt verify /path/to/message.txt /path/to/message.sig /path/to/cert.pem

// Output
Verifying signature...
Signature verification successful

checksum

Calculates the package checksum.

Copied to clipboard.

Usage: vega exec vpt checksum [OPTIONS] <PACKAGE>

Arguments:
  <PACKAGE>     Path to the vpkg

Options:
  -h, --help    Print help

Example:

vega exec vpt checksum /path/to/sampleapp.vpkg

// Output
Calculating checksum...
SHA256: a1b2c3d4e5f6...

generate-csr

Creates a certificate signing request (CSR) from a configuration file.

Copied to clipboard.

Usage: vega exec vpt generate-csr [OPTIONS]

Options:
  -k, --key <KEY>        Private key
  -c, --config <CONFIG>  Config file
  -o, --out <OUT>        Output directory
  -v, --verbose          Print the generated CSR path
  -h, --help             Print help

Example:

vega exec vpt generate-csr -k /path/to/private.key -c /path/to/config.json -o /path/to/output/dir -v

// Output
Reading configuration from config.json
Generating CSR using private.key
CSR created at /output/dir/certificate.csr

Package analysis

These commands validate package structure and contents.

validate

Runs validation checks for AppStore submission requirements:

Validates the package manifest for required configurations and syntactical correctness. See see the manifest user guide.
Validates if the bundled libraries or declared dependencies for your app's native code meets Vega's ABI requirements.

Copied to clipboard.

Usage: vega exec vpt validate [OPTIONS] <PATH>

Arguments:
  <PATH>        Path to the vpkg, directory, or manifest.toml

Options:
      --no-strict-abi-check          Disable strict ABI check
      --no-color                     Disable colored output
  -h, --help                         Print help

Example:

vega exec vpt validate sampleapp.vpkg

// Output
validating 'sampleapp.vpkg' ...
analyzing manifest.toml ...
found issues in manifest.toml ...
manifest validation found 2 errors
manifest.toml:3:1 info: [package.icon] Icon isn't defined in the manifest. Using system default.
  help: Define an icon to help users recognize your app
manifest.toml:15:6 error: [components.interactive.id] Component ID 'com.company.sample.badcomponentname' doesnt have package ID prefix 'com.amazondeveloper.sampleapp'
  help: Component ID should follow the format: package_id.component_name
manifest.toml:9:1 error: [components.interactive.categories] No interactive component declares 'com.amazon.category.main' category. App can't launch without package-id or package ASIN.
  help: One interactive component should declare 'com.amazon.category.main' category in the manifest

starting ABI validation ...
found issues in ABI validation ...
Missing dt_needed dependencies found:
  - Library 'libsample-app.so.0.1.0' at path '/sampleapp/lib/arm/libsample-app.so.0.1.0' has missing dt_needed dependencies: libsample-deps.so
Missing dlopen dependencies found:
  - Library 'libsample-app.so.0.1.0' at path '/sampleapp/lib/arm/libsample-app.so.0.1.0' has missing dlopen dependencies: libsample-deps.so

Create a custom signature for your package

Pull the signature file from the package:

Copied to clipboard.

vega exec vpt pull --json-signature /path/to/sampleapp.vpkg /path/to/output/digest.json.sig

// Output
Extracting signature from sampleapp.vpkg
Signature saved to /path/to/output/digest.json.sig

Update the signature file using your private key and certificate::

Copied to clipboard.

vega exec vpt sign --resign /path/to/input/digest.json.sig /path/to/developer-private.key /path/to/developer-cert.pem /path/to/output/digest.json.sig

// Output
Signing digest.json.sig with provided key and certificate
Signature created at /path/to/output/digest.json.sig

Push the updated signature file back to the package:

Copied to clipboard.

vega exec vpt push --json-signature /path/to/input/digest.json.sig /path/to/sampleapp.vpkg

// Output
Adding signature to sampleapp.vpkg
Signature successfully added

Last updated: Dec 22, 2025

Use VPT for Vega App Packages

Commands

Package information

info

show-contents

Package creation and extraction

pack

unpack

dump

extract-locales

Package signature and verification

pull

push

sign

verify

checksum

generate-csr

Package analysis

validate

Create a custom signature for your package

Related topics