As a Roblox plugin developer, it is currently too hard to know if a package is currently out of date before modifying it. This is because PackageLink.Status is currently restricted to Roblox Script Security instead of Plugin Security.
If Roblox is able to address this issue, it would improve my development experience because I want to implement a warning in my plugin for if a developer tries to modify a package that has a pending update, so that we don’t create version conflicts. The plugin is set up to take care of the hierarchy automatically, so they often don’t see the package status in the Explorer view before working on the asset.
8 Likes
Hey Chief! Let me look for someone to take a look 
7 Likes
The package team talked about this suggestion, and we think that exposing link status or an equivalent property to plugins is a great idea. We may include this in our next round of quality of life improvements. Thanks for bringing this to our attention.
2 Likes
@strange_times +1 to this suggestion. Packages and PackageLink have many problems with Status getting set to Changed for no reason (likely engine bugs). Making Status accessible to Plugins would be a big help to at least allow developers to write plugins to bandaid fix the engine side issues.
In terms of bugs, one of the most frequent/obvious issues is copying and pasting Packages around seems to randomly set Status to Changed even for instances like SurfaceAppearance which can’t even get their position/orientation manipulated by copy-paste. Not sure why copy-paste marks them as dirty.