npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

apk-parser

v0.1.7

Published

Extract Android Manifest info from an APK file.

Downloads

109

Readme

apk-parser - Android apk-file parser

Extract Android Manifest info from an APK file.

Build Status

While there are some implementations for this out in the wild, none of them handle all of the intricacies of the APK file-format. This module uses the aapt tool from the Android SDK to solve that problem. The tool will be downloaded and installed during npm install. Tested on Linux and OS X.

Using 64-bit Ubuntu?

Newer versions of Ubuntu don't support 32-bit executables by default. aapt is a 32-bit executable. In order for apk-parser to work from 64-bit Ubuntu, you need to execute the following commands to install 32-bit support:

sudo dpkg --add-architecture i386
sudo apt-get -qqy update
sudo apt-get -qqy install libncurses5:i386 libstdc++6:i386 zlib1g:i386

Getting started

Add apk-parser to your project: npm install --save apk-parser.

Sample usage:

var parseApk = require('apk-parser');
parseApk('myApkFile.apk', function (err, data) {
    // Handle error or do something with data.
});

The returned data object is an object-representation of the AndroidManifest.xml file. Here's a sample file:

{
    "manifest": [
        {
            "@package": "com.example.android.snake",
            "uses-permission": [
                {
                    "@android:name": "android.permission.INTERNET"
                }
            ],
            "application": [
                {
                    "@android:label": "Snake on a Phone",
                    "activity": [
                        {
                            "@android:theme": "@0x1030006",
                            "@android:name": "Snake",
                            "@android:screenOrientation": 1,
                            "@android:configChanges": "(type 0x11)0xa0",
                            "intent-filter": [
                                {
                                    "action": [
                                        {
                                            "@android:name": "android.intent.action.MAIN"
                                        }
                                    ],
                                    "category": [
                                        {
                                            "@android:name": "android.intent.category.LAUNCHER"
                                        }
                                    ]
                                }
                            ]
                        }
                    ]
                }
            ]
        }
    ]
}

Things to note:

  • The top-level element is a key named manifest.
  • Attributes are encoded by prepending their name with @.
  • Child nodes can be accessed by name. The value is always an array, as there might be more than one array.
  • This representation is unaware of the meaning of this file (you might know that there will always only be one application tag, the module does not). This make sure that it never breaks with future Android releases.

You can increase the buffer size when needed, but do note that it comes with a memory cost:

parseApk('myApkFile.apk', 8 * 1024 * 1024, function (err, data) {
    // Handle error or do something with data.
});

Contributing

All code lives in the lib folder. Try to stick to the style conventions used in existing code.

Tests can be run using grunt test. A convenience command to automatically run the tests is also available: grunt watch. Please add test cases when adding new functionality: this will prove that it works and ensure that it will keep working in the future.

License

(The MIT License)

Copyright (C) 2013-2015 by Ruben Vermeersch <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.