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

stf-device-db

v1.2.0

Published

A smartphone/device database with images for STF.

Downloads

392

Readme

stf-device-db

stf-device-db is a JSON-based database of smartphones, tablets and wearables. The database includes thumbnails for each device and some basic information about the default model at the time of release. It is not complete; currently it mainly covers devices sold in the Japanese market. Data is added as required.

This database is currently being used in STF.

Features

For each device, the following information is provided:

  • Model code (e.g. "SCV31")
  • Product name (e.g. "Galaxy S6 edge")
  • Thumbnail
  • Larger image
  • Carrier (most devices in the Japanese market are carrier-specific models)
  • Manufacturer
  • OS
  • CPU
  • Memory
  • Disk space (if multiple sizes, lowest)
  • Release date (on the Japanese market)
  • Display size

The model code can usually be retrieved from a device quite easily, which then allows fairly straightforward mapping to the device data. Note that some carriers may sometimes prefix models numbers with their own code, which you must strip first.

Sources

The data in this repository is updated regularly from various sources.

  • ULTRAZONE's Japanese smartphone database is currently our main provider for phone data. While their data is not open source, we have asked and obtained a permission to use it. The database is unfortunately limited to phones and does not currently offer useful data for tablets or other devices.
  • Official press releases. We try to keep model-specific sources in CREDITS.md.
  • Manual investigation especially for tablets.

Requirements

On OS X, you can install the last three with:

brew install jq jpegoptim graphicsmagick

Building

Simply run make at the top of the repo after making sure you have the requirements installed. You will then have a complete list of resized icons and photos in the dist folder.

Usage

Install via NPM:

npm install --save stf-device-db

The module is prebuilt before publishing, so you don't need the build requirements if you just want to use the library.

Then you must find your device's model number and possibly the internal product name. On Android, this can be done with:

adb shell getprop ro.product.model
adb shell getprop ro.product.name

The internal product name is not required, but helps make a more specific match for some devices (mainly Nexus devices which reuse the model code for newer models of the same size).

For example, for a Nexus 5 these values would be:

{
  "model": "Nexus 5",
  "name": "hammerhead"
}

You can then require the database and use it to find matching data based on the above values:

var db = require('stf-device-db')

var data = db.find({
  model: 'Nexus 5',
  name: 'hammerhead'
})

data would then be:

{ carrier: { code: 'e', name: 'イー・モバイル' },
  cpu: { cores: 4, freq: 2.26, name: 'Qualcomm Snapdragon 800 MSM8974' },
  date: '2013-11-14T15:00:00.000Z',
  display: { h: 1920, s: 5, w: 1080 },
  maker: { code: 'l', name: 'LG' },
  memory: { ram: 2048, rom: 32768 },
  name: { id: 'Nexus 5', long: 'EM01L' },
  os: { type: 'android', ver: '5.1' },
  image: 'Nexus_5.jpg' }

If no match is found, find() returns null.

Device thumbnails and photos are provided in the dist folder. It can be served as a static folder.

Contributing

See CONTRIBUTING.md.

License

See LICENSE.

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.