Home
Docs
GitHub
Pricing
Blog
Log In

Run Sandworm Audit for your App

Get started
Hold on, we're currently generating a fresh version of this report
Generated on Apr 29, 2024 via pnpm

configstore 0.2.0

Easily load and persist config without having to think about where and how
Package summary
Share
22
issues
3
critical severity
vulnerability
2
license
1
10
high severity
vulnerability
3
license
4
meta
3
5
moderate severity
vulnerability
5
4
low severity
license
4
3
licenses
6
MIT
4
BSD
1
N/A
Package created
13 Nov 2012
Version published
14 Jan 2014
Maintainers
9
Total deps
11
Direct deps
6
License
UNKNOWN

Issues

22

3 critical severity issues

critical
Recommendation: Upgrade to version 1.12.1 or later
via: js-yaml@3.0.2
Recommendation: Upgrade to version 4.17.12 or later
via: lodash@2.4.2
Recommendation: Check the package code and files for license information
via: uuid@1.4.2
Collapse
Expand

10 high severity issues

high
Recommendation: Upgrade to version 4.17.11 or later
via: lodash@2.4.2
Recommendation: Upgrade to version 3.13.1 or later
via: js-yaml@3.0.2
Recommendation: Upgrade to version 4.17.21 or later
via: lodash@2.4.2
Recommendation: Validate that the package complies with your license policy
via: configstore@0.2.0
Recommendation: Validate that the package complies with your license policy
via: js-yaml@3.0.2
Recommendation: Validate that the package complies with your license policy
via: graceful-fs@2.0.3
Recommendation: Validate that the package complies with your license policy
via: osenv@0.0.3
via: graceful-fs@2.0.3
via: mkdirp@0.3.5
via: uuid@1.4.2
Collapse
Expand

5 moderate severity issues

moderate
Recommendation: Upgrade to version 4.17.11 or later
via: lodash@2.4.2
Recommendation: Upgrade to version 3.3.5 or later
via: js-yaml@3.0.2
Recommendation: Upgrade to version 3.13.0 or later
via: js-yaml@3.0.2
Recommendation: Upgrade to version 4.17.21 or later
via: lodash@2.4.2
Recommendation: Upgrade to version 4.17.5 or later
via: lodash@2.4.2
Collapse
Expand

4 low severity issues

low
Recommendation: Read and validate the license terms
via: configstore@0.2.0
Recommendation: Read and validate the license terms
via: js-yaml@3.0.2
Recommendation: Read and validate the license terms
via: graceful-fs@2.0.3
Recommendation: Read and validate the license terms
via: osenv@0.0.3
Collapse
Expand

Licenses

MIT License

Permissive
OSI Approved
This is a human-readable summary of (and not a substitute for) the license. Disclaimer.
Can
commercial-use
modify
distribute
sublicense
private-use
Cannot
hold-liable
Must
include-copyright
include-license
6 Packages, Including:
argparse@0.1.16
js-yaml@3.0.2
lodash@2.4.2
mkdirp@0.3.5
underscore.string@2.4.0
underscore@1.7.0

BSD

Invalid
Not OSI Approved
4 Packages, Including:
configstore@0.2.0
esprima@1.0.4
graceful-fs@2.0.3
osenv@0.0.3

N/A

N/A
1 Packages, Including:
uuid@1.4.2
Disclaimer

This deed highlights only some of the key features and terms of the actual license. It is not a license and has no legal value. You should carefully review all of the terms and conditions of the actual license before using the licensed material.

Sandworm is not a law firm and does not provide legal services. Distributing, displaying, or linking to this deed or the license that it summarizes does not create a lawyer-client or any other relationship.

Direct Dependencies

6
All Dependencies CSV
β“˜ This is a list of configstore 's direct dependencies. Data on all dependencies, including transitive ones, is available via CSV download.
NameVersionSizeLicenseTypeVulnerabilities
graceful-fs2.0.34.9 kBBSD
prod
2
1
js-yaml3.0.230 kBMIT
prod
1
2
2
1
lodash2.4.2192.11 kBMIT
prod
1
2
3
mkdirp0.3.54.06 kBMIT
prod
1
osenv0.0.33.4 kBBSD
prod
1
1
uuid1.4.212.13 kBUNKNOWN
prod
1
1

Visualizations

Frequently Asked Questions

What does configstore do?

Configstore is a convenient npm package that allows users to easily load and persist configurations without worrying about where and how they are stored. The configurations are saved in a JSON file located either in $XDG_CONFIG_HOME or ~/.config.

How do you use configstore?

To use Configstore in your project, first, install the package by using the command $ npm install configstore. Then you can import Configstore into your JavaScript file. You can create a new instance of Configstore using packageJson.name as the packageName and set initial default configurations as the defaults parameter. You can use the .set() function to define configuration value or use the .get() function to retrieve the value of a configuration.

import Configstore from 'configstore';

const packageJson = JSON.parse(fs.readFileSync('./package.json', 'utf8'));

// Create a Configstore instance.
const config = new Configstore(packageJson.name, {foo: 'bar'});

console.log(config.get('foo')); // Outputs 'bar'
config.set('awesome', true);
console.log(config.get('awesome')); // Outputs true

// Use dot-notation to access nested properties.
config.set('bar.baz', true);
console.log(config.get('bar')); // Outputs {baz: true}

config.delete('awesome');
console.log(config.get('awesome')); // Outputs undefined

Where are the configstore docs?

The Configstore documentation can be found in the README file of its GitHub repository: https://github.com/yeoman/configstore. It provides information such as API definitions, package installations, usage examples, and available options. This extensive guide will prove quite beneficial for both beginners and experts looking to implement Configstore in their projects.