
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
TL;DR
Create your Curriculum Vitae (CV) personal webpage by putting your information on a json file and an almost blank index.html (containing just information about themes)
Long Version
When you want to create a personal CV website, you have to put your information into a static HTML file (if you don't want a server based one). Then, if you want to change the design, sometimes changing CSS is not enough; you have to change HTML too. So, this project is meant to:
Technically speaking:
As consequences:
In other word:

For an exhaustive list of available themes, check THIS
To test these themes directly, check THIS
The HTML file doesn't contain anything at all. It just calls for the script which will do the calls.

Check the API
In your project tree, tape this command line to download the latest version to "node_modules":
npm i cv.json
node node_modules/cv.json/install.js
All needed files will be copied to the root (where the shell is positioned)
If you want to test your webpage locally, install a simple HTTP server
npm i http-server -D
Then,
node_modules/http-server/bin/http-server ./ -p 8090
Open this address on your browser:
http://localhost:8090/
By introducing information inside a json file ("cv.json"), you can generate a CV webpage (resumé). This can be done using javascript ("cv.json.js") which is called as follows:
<html>
<head>
<meta charset="UTF-8">
<title>Test CV</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<script type="text/javascript" src="<link/to/cv.json.js>" ></script>
</head>
<body>
<script>
JsonVCard.setStyleName("violet")
.setRelativePath("link/to/current/directory") /*where your profile picture and helper files are*/
.setThemesPath("link/to/the/theme")/*Not affected by setRelativePath*/
.setThemeName("theme-name")/*must come after setThemesPath*/
.setFooter("link/to/footer.htm") /*Not affected by setRelativePath*/
.process("link/to/cv.json");/*Not affected by setRelativePath*/
</script>
</body>
</html>
The json file ("cv.json") contains information about the one for whom we want to generate a CV. it is self explanatory and easy to fill.
For API documentation, check this YuiDoc generated documentation
Also, if you just want to update the package, don't execute the last instruction. Otherwise, it will overwrite your json file (if its name is not cv.json)
All the C's are here:
Copyright (C) 2016-2018 Abdelkrime Aries
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
FAQs
CV webpage dynamically created from a json file and a template
We found that cv.json demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.