awscred

v1.5.0

Resolves AWS credentials (and region) using env, file and IAM strategies

MIT
Latest version published 3 years ago
    npm install awscred
  
We couldn't find any similar packages Browse all packages

Package Health Score

45 / 100

Security

No known security issues
Powered by Snyk
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
1.5.0 | 10/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.4.2 | 11/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.3.0 | 03/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.2.0 | 07/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0 | 06/2015
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test awscred
Get started free

Popularity

Small

Weekly Downloads (5,871)

Download trend
Dependents
28
GitHub Stars
42
Forks
8
Contributors
3

Direct Usage Popularity


The npm package awscred receives a total of 5,871 downloads a week. As such, we scored awscred popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package awscred, we found that it has been starred 42 times, and that 28 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
3
Funding
Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like awscred is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 45/100 package health 45/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
3 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of awscred based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for awscred is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
0 Direct
Versions
10
Install Size
16 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

awscred has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.