Expose repo security status field in ModelInfo
#2639
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, the API response of
https://huggingface.co/api/models/{repo_id}?securityStatus=true
included repo security data in in thesecurityStatus
field. This field was renamed tosecurityRepoStatus
recently on server side, leading to issue reports huggingface/Google-Cloud-Containers#116 & #2638. However, this field wasn't explicitly exposed inModelInfo
. This PR adds it as a field in the dataclass.Changes made
security_repo_status
field to ModelInfo dataclass. This field will contain the value returned by the API insecurityRepoStatus
key.model_info()
'ssecurityStatus
argument to clarify that the security status will be returned inModelInfo.security_repo_status
.@Wauplin I'm not sure if it's a good idea to remove
securityRepoStatus
from the dict (here), this will implicitly "break" things again since users might be using this key already. what do you think?