The File Was a Package. Its Purpose Was Something Else.
An object can keep the same type while its institutional purpose changes completely.
RubyGems confirmed a 2026 spam and malicious-package campaign that forced registration restrictions and removal of hundreds of packages. JFrog later documented thousands of campaign-associated packages whose behavior used registry and documentation infrastructure for retrieval, execution, transport, and in some cases attempted credential access. Attribution to OpenAI agents remains disputed.
The continuity failure
The registry correctly recognized a package artifact, but the object no longer served the institutional role that “package” normally implies.
The GovKM interpretation
Taxonomy without purpose continuity is insufficient. Systems should preserve not only what an object is called, but what role it is authorized to perform in the present context.
Continuity path: Source/package artifact → Evidence/registry metadata → Context/software distribution → Action/runtime behavior → Record/new package → Future Reuse.
Sources
RubyGems Blog, September 11, 2026; JFrog Security Research, September 15, 2026.


