Dependency analysis through class file manipulation

A system comprising:

• a memory;
• and
• a processing device, operatively coupled to the memory, to:
• receive a request for dependency information indicative of one or more class files included in an archive file;
• fetch the archive file from an upstream source, the archive file associated with the dependency information indicative of the one or more class files;
• execute a transformation process to the archive file, the transformation process being applied to indicate provenance information for each of the one or more class files included in the archive file, wherein the provenance information for each of the one or more class files included in the archive file corresponds to bytecode metadata, wherein the bytecode metadata is indicative of the provenance information embedded within the one or more class files;
• scan the archive file for the bytecode metadata to determine specific class files of the one or more class files utilized to build the archive file, wherein the bytecode metadata provides for a tracking of the one or more class files utilized to build the archive file;
• and
• output the archive file to a build module in view of the transformation process that indicates the provenance information for each of the one or more class files included in the archive file.

A non-transitory computer-readable storage medium including instructions that, when executed by a processing device, cause the processing device to:

• receive a request for dependency information indicative of one or more class files included in an archive file;
• fetch the archive file from an upstream source, the archive file associated with the dependency information indicative of the one or more class files;
• execute, by the processing device, a transformation process to the archive file, the transformation process being applied to indicate provenance information for each of the one or more class files included in the archive file, wherein the provenance information for each of the one or more class files included in the archive file corresponds to bytecode metadata, wherein the bytecode metadata is indicative of the provenance information embedded within the one or more class files;
• scan the archive file for the bytecode metadata to determine specific class files of the one or more class files utilized to build the archive file, wherein the bytecode metadata provides for a tracking of the one or more class files utilized to build the archive file;
• and
• output the archive file to a build module in view of the transformation process that indicates the provenance information for each of the one or more class files included in the archive file.