Where did you find this definition of the output?
The Wiki clearly says
"charging_station:output=<xxx> kW – Use this to specify the maximum output of the entire station: This value can often be found on the back of the charge points. For a station with multiple charge points, add them all together for the entire station maximum ouput."
amenity=charging_station

A matching station with a high enough output on a specific socket you can find by looking at the socket:*:output tags.

It's not useful to tag all the sockets that don't exist. Did you check if there is really no socket:cee_red_63a available? Just add the sockets that do exist.

Hi,
you added the new tag "station_deux_roues" here - what does it mean?
node/12794145071

And: Are you sure the output of this station is just 22 kW? That's not really enough to charge 6 cars in parallel.
And: the station is taggd to have no sockets at all which is clearly wrong. Please don't add "socket...=no" tags, just add those that exist, including their count.

Hi, I didn't add any data, this was done in another changeset.

Hi,
please check this street, something went wrong with the parking tags "par" and ":taxi".
way/143057430

Hi,
you used some maxstay and charge tags here that don't seem correct.
E.g.node/7673202253

Checking the pricing scheme of the operator, there is no maxstay, but just a fee if you stay longer than a certain time.

Also, the price doesn't seem to be right for this high-powered charging station.
There's no low-power connector available, so there's no charging below 0.78EUR/kWh possible.
The prices also don't change depending on AC or DC, but just on the power available.

Lastly, I would not tag the charging prices - they tend to change way too often and depend on way to many factors to be maintained in OSM. Just link to the very simple and concise document of the operator.

Hi,
the tags
access = per_ipovedenti
segnaletica_accessibile = Sì
are not commonly used. Could you explain which infrastructure is existing here that helps the blind?

Hi,
please don't try to dump data from an external source into OSM.
All these tags should not appear in OSM:
block=-1
color24=-1
colour=0,0,0,7
etype=18
handle=896
linewidth=0
ltscale=1
lweight=-1
name=TRACKER
ocolor=256
olinetype=continuous
space=0
thickness=0
transparen=0
visible=1
width=0

Also, your user name and the 'operator' tag suggest that you are doing these edits somewhat officially. If so, the "organised mapping guidelines" may apply:
osm.wiki/Organised_Editing_Guidelines

The tags along with the accuracy also make it seem that the source (Ortosat) might not be correct.

And lastly, you added fences on top of existing tracks, blocking them. Please check which of the objects is in the right position.

Hi,
please check the wiki about how to map charging stations.
None of these tags is correct:

charge-capacity
charging_capacity
charge_capacity
num_stations
num-station
num-stations
num_sations

amenity=charging_station#Examples

That's not access=permissive - that means that someone tolerates people accessing the way without asking, but has can revoke this right at any time.

access=private would be appropriate - someone decides on a case-by-case basis who is allowed to enter.

Hi,
please check this way, it didn't get any proper tags:
way/1378582103

See e.g.
https://community.openstreetmap.org/t/opinions-on-internet-access-password/117581

The pure existence of such a code implies that the door is not meant to be used by everyone. If they distribute the code to all their customers, that is their decision, but making the information public to everyone in the world is likely not their intention.

Just take this example:
node/12741716368

The next town is ten kilometers away and Bundibugyo district is even further away.

I checked 5 more nodes - non of them is even remotely close to the place the addr:* tags claim it to be. Not even in the same district.

This import definitely has to be reverted.

What about all the other non-standard tags?

floors
materials
resources
sections
services

There are also libraries in the middle of a lake or on top of an uninhabited mountain.

No matter what the source of this data is, the large scale of the edit makes it an import that needs to be properly documented.

Hi,
you used this tag on two stone:
"inscription:direction_east"
I think this should either be
inscription:E or direction_east, but not a combination of both. It's highly unlikely that any tool will be able to interpret this tag.

Hi,
you added some strange tags like "OBTC = UAIBIT". Could you explain what they are supposed to mean?

Fine with me - but the 'danger' key was added somewhere else:
changeset/163883089

Hi,
it seems something went wrong with this import of libraries.
First of all, we're missing the mandatory source and description of the import, see
osm.wiki/Import/Guidelines

Second, there are many tags that are not used in any other place and should be replaced by proper ones.

For now I suggest to revert this import, so that it can be redone with proper tagging and attribution.

Hi,
could you check this building? It got a strange 'shutter' tag.
way/85994237#map=19/43.786039/5.762005