Skip to content

Releases: thoughtworks/talisman

Adding support for custom patterns in filecontent detection

12 Mar 10:21
6e6178b
Compare
Choose a tag to compare
#183 Custom patterns  (#187)

* Rename TalismanRCIgnore to TalismanRC

* Code cleanup:
Rename NewtalismanRC to NewTalismanRC
Remove code and tests related to talismanignore

* Code cleanup: Make talismanRC receiver name consistent

* Introduce PatternString type
Omit empty fields when writing yaml

* #183 | Add ability to specify custom scan pattern via talismanrc

* Update Readme:
Update help text for CLI options (fix typo in -i message description)
Add custom_pattern section with example

Hacktoberfest contributions

20 Nov 02:57
Compare
Choose a tag to compare
  • Performance improvements
  • Talisman binary can be invoked in interactive mode to updated talismanrc

Add feature to permanently ignore files based on a scope

02 Oct 07:27
Compare
Choose a tag to compare

Talisman now supports permanently ignoring certain files using an idea called scopes.
A scope defines a set of files that will be ignored by talisman during scans.
There a currently a few hard-coded set of scopes (node, go to support nodeJS and Go-lang respectively). Users cannot create their own scopes.
A guideline for adding scopes vi github Pull Request's is being prepared.

Added scanning for a new pattern PWD=xxxxxxxx

12 Aug 17:34
2ec54f6
Compare
Choose a tag to compare
Merge pull request #131 from harinee/master

Deleting .talismanignore as it is deprecated now

Fixed recurring update issue

13 Aug 10:13
Compare
Choose a tag to compare
v0.4.9

Fixed Talisman header in readme

Talisman HTML reporting is now active

13 Aug 10:13
136ca89
Compare
Choose a tag to compare

This release introduces talisman scan reports in HTML

v0.4.7: Merge pull request #121 from jaydeepc/master

13 Aug 10:13
136ca89
Compare
Choose a tag to compare
Changed the Author Name, no code changes included

Fixed scan logic when checksum is not matching

20 Mar 22:54
Compare
Choose a tag to compare

This release fixes a bug in the scanning logic of Talisman

Adds summary section to JSON in scan report

13 Mar 09:57
Compare
Choose a tag to compare
  • Now the summary section in JSON report is populated
  • Code has been refactored to accommodate further changes

Generate scan report in JSON and modify the scan logic

11 Mar 08:56
Compare
Choose a tag to compare
  • Now, users can generate scan report in JSON format and store it in a custom location
  • The scan logic has now been updated to scan only the diff for each file if Talisman is being used as a pre-commit hook.
  • Stops the scan in scenarios where the checksum of the file is matching