npmpackage.info

Gathering detailed insights and metrics for cson-parser

cson-parser - 4.0.9 | npmpackage.info

cson-parser

Simple & safe CSON parser

4.0.9

133

BSD-3-Clause

JavaScript

3.1

Installations

npm install cson-parser

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Min. Node Version

>=10.13

Node Version

14.16.0

NPM Version

6.14.11 Pull Requests

Open

6

Total

62

Closed

13

Merged

43

Issues

Open

13

Total

38

Closed

25

Releases

v4.0.9

Updated on Mar 26, 2021

v4.0.8

Updated on Feb 17, 2021

v4.0.7

Updated on Nov 23, 2020

v4.0.6

Updated on Nov 19, 2020

v4.0.5

Updated on Jul 20, 2020

v4.0.4

Updated on Feb 03, 2020

View All 18 releases

Languages

JavaScript

JavaScript (100%)

Developer

groupon

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

BSD-3-Clause License

133 Stars

152 Commits

27 Forks

9 Watchers

8 Branches

17 Contributors

Updated on Apr 28, 2025

Maintainers

View All 17 Contributors

Package Meta Information

Latest Version

4.0.9

Package Id

cson-parser@4.0.9

Size

8.35 kB

NPM Version

6.14.11

Node Version

14.16.0

Published on

Mar 26, 2021

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

coffeescript

Dev Dependencies

c8 eslint eslint-config-groupon eslint-plugin-import eslint-plugin-mocha eslint-plugin-node eslint-plugin-prettier mocha nlm npm-run-all prettier

cson-parser

A minimalistic CSON parser. Offers:

A strict subset of CSON that allows only data
Interface is identical to JSON.{parse,stringify}
Does not run the code, free of intermediate string representations
Sane parse error messages with line/column
Regular Expressions are considered data and will be accepted as well

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

Install

npm install --save cson-parser

Usage

1CSON = require 'cson-parser'
2# This will print { a: '123' }
3console.log CSON.parse "a: '123'"

High-level APIs

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 files
CSON, provides file, coffeescript, javascript handling and a CLI
season, atom.io's CSON package. Includes CLI tool to convert CSON to JSON
grunt-cson, converts CSON to JSON as a grunt task
load-grunt-configs, loads grunt config from CSON files (among other formats)
fetcher, a declarative way to download (frontend) libraries, supports CSON configs
csonschema, parses JSON Schema files written in CSON

You can find more on the npm website.

FAQ

Why not just use YAML?

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.

Why not just use JSON?

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.

Why not just use CoffeeScript directly?

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.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

4

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

3.1

/10

Last Scanned on 2025-07-07

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