https://github.com/google/node-sec-roadmap

Some thoughts on how Node.js might respond to a changing security environment
https://github.com/google/node-sec-roadmap

gitbook nodejs security

Last synced: 3 months ago
JSON representation

Some thoughts on how Node.js might respond to a changing security environment

• Host: GitHub
• URL: https://github.com/google/node-sec-roadmap
• Owner: google
• License: other
• Archived: true
• Created: 2017-12-13T17:50:56.000Z (about 7 years ago)
• Default Branch: master
• Last Pushed: 2019-02-01T11:08:13.000Z (almost 6 years ago)
• Last Synced: 2024-08-02T06:24:47.854Z (6 months ago)
• Topics: gitbook, nodejs, security
• Language: JavaScript
• Homepage: https://nodesecroadmap.fyi/
• Size: 479 KB
• Stars: 172
• Watchers: 17
• Forks: 29
• Open Issues: 5
• Metadata Files:
  • Readme: README.md
  • Contributing: CONTRIBUTING.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-repositories - google/node-sec-roadmap - Some thoughts on how Node.js might respond to a changing security environment (JavaScript)

README

        
# Node.js Security Roadmap

The security roadmap is a [gitbook](https://toolchain.gitbook.com/)

publication available at

*[nodesecroadmap.fyi](https://nodesecroadmap.fyi)*.

```sh

$ npm start

```

will serve the book via `localhost:4000`.

```sh

$ make help

```

will display help information about other options.

Please file errata at the

[issue tracker](https://github.com/google/node-sec-roadmap/issues)

or send us a pull request.

If you'd like to help out, please also see our

[contribution guidelines](CONTRIBUTING.md).