-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Citi hackathon code submission #809
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chore(deps): update dependency mocha to v10.7.0
….x-lockfile fix(deps): update dependency express-rate-limit to v7.4.0
docs: adding Zoom meeting and mailing list to README
docs: install a local checkout
chore(deps): update dependency husky to v9.1.3
chore(deps): update dependency @babel/eslint-parser to v7.25.0
chore(deps): update dependency @babel/eslint-parser to v7.25.1
chore(deps): update dependency husky to v9.1.4
chore: v1.3.3
chore(deps): update dependency @babel/core to v7.25.2
…lock feat: format violation text output on a blocked push
chore: version bump patch to v1.5.2
fix: sync issue between dependency manifest in package-lock.json and package.json
Exports makes it hard to access other paths in the project Until we arrive on stable interfaces to access other parts of git-proxy removing exports would be helpful. Import paths have been adjusted slightly for plugins and the docs for plugins due to the exports aliases being a bit different.
chore: bump minor version to 1.6.0
✅ Deploy Preview for endearing-brigadeiros-63f9d0 canceled.
|
@JamieSlome @coopernetes we were working on some refactor on #798 PR and due to some merge conflicts we had to rollback and the PR got closed this PR contains all the commits from 14-11-2024 and before please consider this as our submission . There is some issue with no of commits but files changed are appropriate and the code is working which we will demonstrate during our presentation. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR can be considered as a submission for the FinOS CitiHackathon.
Team members:
This PR solves issue #745 #788 #796 #797 #765
GITPROXY PLUGINS
We have worked on the following features :
.json
,.xlsx
,.csv
).jpg
,.jpeg
,.tiff
)Some Modifications for the Gitleaks and Non-Standard Cryptography Usage are required.
Sensitive Data Detection ( in files like
.json
,.xlsx
,.csv
)Features:
This solves issue #745
proxy.config.json
with the file types for which sensitive data detection is required, for ex:Check EXIF Metadata from Images (
.jpg
,.jpeg
,.tiff
)Features:
This solves issue #796
proxy.config.json
with the file types for which EXIF Metadata needs to be detected.Detection of AI/ML usage (incl. weights, models etc.)
Features:
This solves issue #788
proxy.config.json
with the parameters for which detection needs to be carried out.Vulnerability Detection using GitLeaks
Features:
This solves issue #797
gitleaks.toml
fileproxy.config.json
to enable / disable the plugin.gitleaks_reports.json
Detection of Non-Standard Cryptography Usage
This solves issue #765
Features: