Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

Side note: we should probably show the date with a standard format.

Side note: we should probably show the date with a standard format.

Should we not rather stay consistent with the lastLogin attribute which is also reported in timestamp format?

Another possibility would be to also convert lastLogin but in this case we need to consider the case where it is set to 0 (user has not performed the first login yet) which otherwise would be converted to January 1, 1970 when using the formatDateTime method.

$ php occ user:list -s
...
  - harry:
    - uid: harry
    - displayName: harry
    - email: harrydavis@example.com
    - quota: default
    - enabled: true
    - lastLogin: 1689843012
    - creationTime: 0
    - home: /home/phil/git/owncloud/core/data/harry
    - backend: Database
    - cloudId: harry@localhost
    - searchTerms:
...
  - user1:
    - uid: user1
    - displayName: user1
    - email
    - quota: default
    - enabled: true
    - lastLogin: 1679373156
    - creationTime: 1679372958
    - home: /home/phil/git/owncloud/core/data/user1
    - backend: Database
    - cloudId: user1@localhost
    - searchTerms:

creationTime is already reported in the full listing as a Unix timestamp number. I have some older users that have a zero creation time (that is from the past before this attribute was recorded). So adjusting the output format of login time and creation time is a separate issue - if someone thinks that there is a requirement/need for that.