Gathering detailed insights and metrics for dxccjs
Gathering detailed insights and metrics for dxccjs
npm install dxccjs
Typescript
Module System
Node Version
NPM Version
65.6
Supply Chain
72
Quality
75
Maintenance
50
Vulnerability
80.9
License
JavaScript (100%)
Total Downloads
676
Last Day
1
Last Week
3
Last Month
15
Last Year
124
4 Commits
2 Watching
1 Branches
1 Contributors
Minified
Minified + Gzipped
Latest Version
0.0.1
Package Id
dxccjs@0.0.1
Unpacked Size
6.54 MB
Size
460.72 kB
File Count
6
NPM Version
6.1.0
Node Version
10.1.0
Cumulative downloads
Total Downloads
Last day
0%
1
Compared to previous day
Last week
50%
3
Compared to previous week
Last month
150%
15
Compared to previous month
Last year
57%
124
Compared to previous year
1
A lightweight utility to determine the dxcc entity information from a callsign's prefix
This is my second NPM package, and I'm relatively new to Javascript. As I learn, breaking changes are not only possible, but likely. If you have feedback, I would love to hear it.
npm install dxccjs
Using the included file in ./data/cty.xml (current as of July 10, 2018, courtesy of ClubLog), you can instantiate a new instance of dxccjs and check a callsign as follows.
let dxcc = new dxccjs('./data/cty.xml')
asdf.on('loaded', () => {
console.log( dxcc.checkCall('LU1EEP') )
})
Since it may take some time to parse the XML file, the loaded
event is triggered when it has finished loading. Checking a call will result in the following object being returned:
{ '$': { record: '1722' },
call: [ 'LU' ],
entity: [ 'ARGENTINA' ],
adif: [ '100' ],
cqz: [ '13' ],
cont: [ 'SA' ],
long: [ '-58.4' ],
lat: [ '-34.6' ] }
If a matching prefix is not found, { }
is returned.
Tests are coming soon.
This is my second npm module. Send me PRs or comments. I'm here to learn!
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
1 existing vulnerabilities detected
Details
Reason
no SAST tool detected
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/4 approved changesets -- score normalized to 0
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2025-01-27
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