I just noticed on Framework 2.4.0 and Authoring Tool 0.10.1 that a published course contains all assets of the themes it previously was published or previewed with.
So let’s have a course with theme A, publish it, change it to theme B and publish it again. The SCORM will contain theme B’s assets as it should, but it also includes all of theme A’s assets! I did notice this behavior because of a course that was a copy of another one but changed themes in the meantime.
This issue is fixed in Framework 5.3.0 and Authoring Tool 0.10.3 but might be available in other versions. The source files never were affected (so a manual build was OK), but for those of us that mainly use the published SCORM.zip of the Authoring Tool, it will look unprofessional if assets of another customers (like logos, images, fonts etc.) are included in the SCORM.