Starting from version 12.12.0, Node.js offers built-in support for translating error stack traces using source maps - learn more here: https://medium.com/@nodejs/source-maps-in-node-js-482872b56116

Let's rework @loopback/build to use this new feature on recent version of Node.js, instead of source-map-support module.

If it's possible, then implement a fallback to npm module `source-map-s

We could add the following rules (https://github.com/sbousseaden/YaraHunts) to the default Yara rules available

Information

For the hacktoberfest and to prepare the v6, you can easily find typo on this branch/PR:

https://github.com/TypedProject/tsed/pull/941/files

If you find typo, create branch from https://github.com/TypedProject/tsed/tree/v6-update-documentation, then create PR on
this branch. I'll merge it quickly :)

Pages can be reviewed

• [Getting started](https://github.com/

建议BaseRepository 里增加返回 IQueryable 的Get / GetAsync 的方法
有了之后就可以在service 里面进行拼接LINQ 用于获取到ViewModel中关联其他类的数据

Most .py files use #!/usr/bin/python3 as shebang, but few others use #!/usr/bin/env python3.

Files which use #!/usr/bin/env python3:

./contrib/eventdb/common.py
./intelmq/bin/intelmq_generate_misp_objects_templates.py
./intelmq/tests/bots/parsers/github_feed/test_parser.py

These files should use #!/usr/bin/python3 for the sake of consistency.