Merge pull request #270 from i0natan/6.1_fixes

MINOR Add tslint-config-security MINOR eslint-config-security image
goldbergyoni · Oct 17, 2018 · 5600c89 · 5600c89
2 parents b2858a5 + 53cf4c7
commit 5600c89
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 1 deletion.
diff --git a/assets/images/eslint-plugin-security.png b/assets/images/eslint-plugin-security.png
diff --git a/sections/security/lintrules.md b/sections/security/lintrules.md
@@ -2,7 +2,7 @@
 
 ### One Paragraph Explainer
 
-Security plugins for ESLint such as [eslint-plugin-security](https://github.com/nodesecurity/eslint-plugin-security) offer code security checks based on a number of known vulnerabilities, such as unsafe RegEx, unsafe use of `eval()`, and non-literal filenames being used when accessing the file system within an application. The use of git hooks such as [pre-git](https://github.com/bahmutov/pre-git) allows to further enforce any rules on source control before they get distributed to remotes, one of which can be to check that no secrets were added to source control.
+Security plugins for ESLint and TSLint such as [eslint-plugin-security](https://github.com/nodesecurity/eslint-plugin-security) and [tslint-config-security](https://www.npmjs.com/package/tslint-config-security) offer code security checks based on a number of known vulnerabilities, such as unsafe RegEx, unsafe use of `eval()`, and non-literal filenames being used when accessing the file system within an application. The use of git hooks such as [pre-git](https://github.com/bahmutov/pre-git) allows to further enforce any rules on source control before they get distributed to remotes, one of which can be to check that no secrets were added to source control.
 
 ### `eslint-plugin-security` example