Gathering detailed insights and metrics for fill-keys
Gathering detailed insights and metrics for fill-keys
Fill keys in a destination that are defined on the source
Installations
npm install fill-keysReleases
Unable to fetch releases
Developer
bendrucker
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
>= 16
Typescript Support
No
Node Version
18.7.0
NPM Version
8.15.0
Statistics
33 Commits
1 Forks
3 Watching
4 Branches
2 Contributors
Updated on 14 Oct 2022
Bundle Size
833.00 B
Minified
412.00 B
Minified + Gzipped
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
157,092,202
Last day
-4.1%
117,650
Compared to previous day
Last week
2.6%
739,601
Compared to previous week
Last month
24.2%
2,839,552
Compared to previous month
Last year
-5.5%
25,644,486
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
2
Versions
fill-keys
Fill keys in a destination that are defined on the source. Copies descriptors so properties like
enumerablewill persist.
Install
$ npm install --save fill-keys
Usage
1const fillKeys = require('fill-keys') 2 3fillKeys(destination, source); 4//=> missing destination keys in source are copied
fill-keys will copy descriptors. It will also copy the source.prototype properties onto destination.prototype if both destination and source are functions.
API
fillKeys(destination, source) -> destination
destination
Required
Type: any
The destination object where keys from source will be added.
source
Required
Type: any
The source object from which to copy properties.
License
MIT © Ben Drucker
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: license:0
- Info: FSF or OSI recognized license: MIT License: license:0
Reason
Found 3/21 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:11: update your workflow using https://app.stepsecurity.io/secureworkflow/bendrucker/fill-keys/test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:12: update your workflow using https://app.stepsecurity.io/secureworkflow/bendrucker/fill-keys/test.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:16
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 12 are checked with a SAST tool
Score
3.5
/10
Last Scanned on 2024-11-25
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