Gathering detailed insights and metrics for cson-parser
Gathering detailed insights and metrics for cson-parser
Gathering detailed insights and metrics for cson-parser
Gathering detailed insights and metrics for cson-parser
npm install cson-parser
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
133 Stars
152 Commits
27 Forks
10 Watching
8 Branches
15 Contributors
Updated on 01 Oct 2024
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
-5.3%
30,903
Compared to previous day
Last week
2%
177,705
Compared to previous week
Last month
5%
742,829
Compared to previous month
Last year
-30.3%
8,867,578
Compared to previous year
A minimalistic CSON parser. Offers:
In addition of pure data it allows for simple arithmetic expressions like addition and multiplication. This allows more readable configuration of numbers, the following is a valid strict CSON file:
1cachedData: 2 refreshIntervalMs: 5 * 60 * 1000
npm install --save cson-parser
1CSON = require 'cson-parser' 2# This will print { a: '123' } 3console.log CSON.parse "a: '123'"
cson-parser
only offers basic parsing and serialization.
But there are some great tools if you want more than that:
fs-cson
, read and write CSON filesCSON
, provides file, coffeescript, javascript handling and a CLIseason
,
atom.io's CSON package.
Includes CLI tool to convert CSON to JSONgrunt-cson
,
converts CSON to JSON as a grunt taskload-grunt-configs
,
loads grunt config from CSON files (among other formats)fetcher
,
a declarative way to download (frontend) libraries, supports CSON configscsonschema
,
parses JSON Schema files written in CSONYou can find more on the npm website.
YAML allows for some pretty complex constructs like anchor and alias, which can behave in unexpected ways, especially with nested objects. CSON is simpler while still offering most of the niceties of YAML.
JSON doesn't offer multi-line strings and is generally a little noisier. Also sometimes it can be nice to have comments in config files.
You don't want data files being able to run arbitrary code.
Even when ran in a proper sandbox, while(true)
is still possible.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 6/13 approved changesets -- score normalized to 4
Reason
dependency not pinned by hash detected -- score normalized to 3
Details
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
13 existing vulnerabilities detected
Details
Score
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