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

libbagbak

v2.5.0

Published

The library port of bagbak.

Downloads

2

Readme

libbagbak

The library port of bagbak. The version will be updated as bagbak updates, and all thanks should be go for the bagbak contributors.

  • 📦 Bundling ready
  • ✨ Fully typed

Usage

Warning This library only supports ESM format.

You can try out the following example after cloning this repository via pnpm ts-node-esm ./example/index.js after connecting Frida device via USB.

import {useUsbDevice} from 'libbagbak/device.js';
import {pull} from 'libbagbak';

(async () => {
	const device = await useUsbDevice();

	for (let i = 0; i < 5; i++) {
		const hasFailed = await pull(device, {
			hint: 'com.nexon.bluearchive',
			outdir: './dump',
			useExtensions: true,
			useColdBootedApplication: true,
		})
			.catch(error => {
				console.error(error);

				return true;
			});

		if (!hasFailed) {
			break;
		}
	}
})();

The pull function takes Frida Device and options to pull out decrypted application from the device. In the output directory, you'll see the following directory structure: {outdir}/Payload/{applicationName}/.

See the followings for the options:

Pulling options

  • hint (string) The application bundle identifier. (Example: com.8bit.bitwarden, com.nexon.bluearchive)
  • outdir (string) The output directory.
  • useExtensions (boolean) true if you want to decrypt extensions. (Optional, Default: true)
  • useColdBootedApplication (boolean) true if you want to kill the target application if already opened. (Optional, Default: true)

Exporting as IPA

The IPA file format is basically same as zip. You can use adm-zip for zipping on Node.JS.

We won't handle zipping it on here to make the library portable.

Development

We match the original bagbak version and use submodules for code access. See scripts/build.sh for more information how libbagbak references bagbak's code.

License

The license of this project is same with the original repository (bagbak), and distributed under MIT license.