feat: add a timestamp validation check #850
Open
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
The timestamp check is the Macaron specific implementation of the timestamp heuristic that was developed as part of my research thesis. The check compares the published time of the Maven package recorded on the Maven Central registry to the time identified by Macaron's Commit Finder. Once the difference in the time is identified, it persists all the packages with a time difference greater than 24 hours onto the database as potential malicious packages. This is following the findings from the extensive benchmark analysis done as part of the research thesis. Signed-off-by: Anshul Dadhwal <[email protected]>
oracle-contributor-agreement
bot
added
the
OCA Verified
behnazh-w
changed the title
Signed-off-by: Trong Nhan Mai <[email protected]>
Signed-off-by: Ben Selwyn-Smith <[email protected]>
) Pylint version 3.3.0 has added a new check too-many-positional-arguments, which is causing our linter checks to fail. This PR disables this check similar to other opinionated too-many-* checks. Signed-off-by: behnazh-w <[email protected]>
Signed-off-by: behnazh-w <[email protected]>
…nd make dependency resolution off by default (oracle#840) Signed-off-by: Trong Nhan Mai <[email protected]>
Signed-off-by: Ben Selwyn-Smith <[email protected]>
Signed-off-by: Ben Selwyn-Smith <[email protected]>
The timestamp check is the Macaron specific implementation of the timestamp heuristic that was developed as part of my research thesis. The check compares the published time of the Maven package recorded on the Maven Central registry to the time identified by Macaron's Commit Finder. Once the difference in the time is identified, it persists all the packages with a time difference greater than 24 hours onto the database as potential malicious packages. This is following the findings from the extensive benchmark analysis done as part of the research thesis. Signed-off-by: Anshul Dadhwal <[email protected]>
…l/macaron into timestamp-heuristic
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.
The timestamp check is the Macaron specific implementation of the timestamp heuristic that was developed as part of my research thesis. The check compares the published time of the Maven package recorded on the Maven Central registry to the time identified by Macaron's Commit Finder.
Once the difference in the time is identified, it persists all the packages with a time difference greater than 24 hours onto the database as potential malicious packages. This is following the findings from the extensive benchmark analysis done as part of the research thesis.