npmpackage.info

Gathering detailed insights and metrics for packument

Other packages similar to packument

query-registry

4.0.1

Query the npm registry for packuments, manifests, packages and download counts

packument-package

2.0.0

Fetch package metadata of a version from the npm registry

lumaxis-packument-test

1.0.0

@vltpkg/pick-manifest

0.0.0-17

Choose a manifest from a packument

Gathering detailed insights and metrics for packument

packument - 2.0.0 | npmpackage.info

packument

Fetch package metadata from the npm registry

2.0.0

MIT

JavaScript

5.77 kB

3.8

Installations

npm install packument

Developer Guide

BETA

Typescript

No

Module System

N/A

Min. Node Version

>=10

Node Version

16.9.1

NPM Version

7.21.1 Pull Requests

Open

2

Total

7

Closed

3

Merged

2

Issues

Open

0

Total

1

Closed

1

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

vweevers

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

2 Stars

12 Commits

1 Watchers

3 Branches

1 Contributors

Updated on Mar 07, 2023

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

2.0.0

Package Id

packument@2.0.0

Unpacked Size

5.77 kB

Size

2.63 kB

File Count

NPM Version

7.21.1

Node Version

16.9.1

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

registry-auth-token registry-url simple-get

Dev Dependencies

nock standard tape

packument

Fetch package metadata from the npm registry. Supports scopes and private registries. If you only need the metadata of a specific version, use packument-package.

example

1const packument = require('packument')
2
3packument('levelup', (err, result) => {
4  if (err) throw err
5  console.log(result.versions['2.0.2'].dependencies)
6})

`packument(name[, opts], callback)`

Callback receives an error if any, a packument and response headers. Options:

headers: custom headers (you can override any)
keepAlive: shortcut for headers: { connection: 'keep-alive' }
full: if true, fetch full metadata rather than an abbreviated document.

`packument = packument.factory(opts)`

Preconfigure the function. For example, to always fetch full metadata:

1const packument = require('packument').factory({ full: true })
2
3packument('levelup', (err, result) => {
4  if (err) throw err
5  console.log(result._rev)
6})

Combine it with an in-memory cache:

1const memoize = require('thunky-with-args')
2const packument = memoize(require('packument').factory({ full: true }))
3
4packument('levelup', (err, result) => {
5  // It will make only one request
6})
7
8packument('levelup', (err, result) => {
9  // Subsequent calls for the same package are cached
10})

Reuse that cache in other modules:

1const memoize = require('thunky-with-args')
2const packument = memoize(require('packument'))
3const getPackage = require('packument-package').factory(packument)
4
5getPackage('levelup', '~2.0.0', function (err, pkg) {
6  if (err) throw err
7  console.log(pkg.version)
8})

install

With npm do:

npm install packument

license

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Maintained

Determines if the project is "actively maintained".

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

SAST

Determines if the project uses static code analysis.

Score

3.8

/10

Last Scanned on 2025-06-30

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More