Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Consider adding ability to scan all samples with new modules #93
Labels
Comments
|
Are you thinking we would just update the most recent report? One issue I can think of is that a report is kinda a snapshot in time (e.g., available AV signatures, YARA signatures, general scanning module capabilities). It might somewhat pollute the report to add a module 6 months (or whatever) after the fact. |
|
I've heard a few more requests for this. Let's come up with an implementation strategy. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Should we have an option to rescan all samples? So if you added a new module, you can get updated reports on all the samples you previously analyzed.