scriptex / freelance-salary-calculator

Salary calculator for contractors and freelancers (based on the Bulgarian Labour Law)

Hi, I'm Atanas 👋

• Javascript/Typescript engineer doing Web and Mobile front-end development since 2011
• Lead front-end developer at dmarcian
• Former senior software developer and mentor at Three11
• Former lead front-end engineer in the E.ON Home project
• Former senior web and desktop applications developer at Kinetik Automotive
• Former senior front-end engineer and mentor at 2create
• Former senior front-end developer at htmlBurger
• Former senior front-end developer at htmlBoutique
• Former front-end developer at HTML Lab
• Part of "the top 3% in the world" at Toptal
• Founding talent member at Braintrust
• Senior front-end engineer at Andela
• Freelance Javascript/Typescript Engineer at Upwork
• Freelance Javascript/Typescript Engineer at Freelancer
• Freelance front-end engineer at 9am
• Freelance front-end developer at Wellfound
• Senior front-end engineer at People Per Hour
• Freelance front-end developer at FlexWork
• Freelance front-end developer at Arc.dev
• Freelance front-end developer at Codementor
• Open source software maintainer - check my projects.
• Author of web components at WebComponents.org
• Author of browser extensions for Google Chrome and Mozilla Firefox
• Google developer

My open source software is published on NPM and has been downloaded this many times in the past year:

Here is a bit more detailed graph showing my open source contributions in the past year:

Wondering how to pronounce my name? Not anymore!

---

Connect with me:

                     

---

Support and sponsor my work:

freelance-salary-calculator's Issues

Misalignment between this app and KiK.info

See attached PDF file in the LinkedIn discussion

CVE-2022-46175 (High) detected in json5-1.0.1.tgz, json5-2.2.1.tgz

CVE-2022-46175 - High Severity Vulnerability

Vulnerable Libraries - json5-1.0.1.tgz, json5-2.2.1.tgz

json5-1.0.1.tgz

JSON for humans.

Library home page: https://registry.npmjs.org/json5/-/json5-1.0.1.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/json5/package.json

Dependency Hierarchy:

• eslint-config-next-13.1.1.tgz (Root Library)
  • eslint-plugin-import-2.26.0.tgz
    • tsconfig-paths-3.14.1.tgz
      • ❌ json5-1.0.1.tgz (Vulnerable Library)

json5-2.2.1.tgz

JSON for humans.

Library home page: https://registry.npmjs.org/json5/-/json5-2.2.1.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/json5/package.json

Dependency Hierarchy:

• core-7.20.7.tgz (Root Library)
  • ❌ json5-2.2.1.tgz (Vulnerable Library)

Found in base branch: main

Vulnerability Details

JSON5 is an extension to the popular JSON file format that aims to be easier to write and maintain by hand (e.g. for config files). The parse method of the JSON5 library before and including version 2.2.1 does not restrict parsing of keys named __proto__, allowing specially crafted strings to pollute the prototype of the resulting object. This vulnerability pollutes the prototype of the object returned by JSON5.parse and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations. This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from JSON5.parse. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution. JSON5.parse should restrict parsing of __proto__ keys when parsing JSON strings to objects. As a point of reference, the JSON.parse method included in JavaScript ignores __proto__ keys. Simply changing JSON5.parse to JSON.parse in the examples above mitigates this vulnerability. This vulnerability is patched in json5 version 2.2.2 and later.

Publish Date: 2022-12-24

URL: CVE-2022-46175

CVSS 3 Score Details (7.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: Low
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2022-46175

Release Date: 2022-12-24

Fix Resolution: json5 - 2.2.2

---

Step up your Open Source Security Game with Mend here

CVE-2023-2251 (High) detected in yaml-1.10.2.tgz

CVE-2023-2251 - High Severity Vulnerability

Vulnerable Library - yaml-1.10.2.tgz

JavaScript parser and stringifier for YAML

Library home page: https://registry.npmjs.org/yaml/-/yaml-1.10.2.tgz

Path to dependency file: /package.json

Path to vulnerable library: /node_modules/yaml/package.json

Dependency Hierarchy:

• styled-11.10.6.tgz (Root Library)
  • babel-plugin-11.10.6.tgz
    • babel-plugin-macros-3.1.0.tgz
      • cosmiconfig-7.1.0.tgz
        • ❌ yaml-1.10.2.tgz (Vulnerable Library)

Found in HEAD commit: 888a26d9e010d374a773819e90cc64e3046b63da

Found in base branch: main

Vulnerability Details

Uncaught Exception in GitHub repository eemeli/yaml prior to 2.2.2.

Publish Date: 2023-04-24

URL: CVE-2023-2251

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-f9xv-q969-pqx4

Release Date: 2023-04-24

Fix Resolution: yaml - 2.2.2

---

Step up your Open Source Security Game with Mend here