So I'm not part of the pcf team jsut the guy who suggested it,
but I think the issue here is the owners of the projects that list here are not using tools like this, the project in github is their responsibility and in some cases they are abandoned or they just don't know to do this.
Its why I suggested indicators, this warns users of the components the current state at least.
Ive spoke with folk in ms about this and they are of a similar opinion to myself that the best way to utilise pcf components is to fork it and do all of those checks and tasks yourself including a full code review of the component as ultimately you are putting 3rd party code in your tenant.
Having such an indicator is also a way to encourage authors to do these tasks and do regular updates.
So I'm not part of the pcf team jsut the guy who suggested it,
but I think the issue here is the owners of the projects that list here are not using tools like this, the project in github is their responsibility and in some cases they are abandoned or they just don't know to do this.
Its why I suggested indicators, this warns users of the components the current state at least.
Ive spoke with folk in ms about this and they are of a similar opinion to myself that the best way to utilise pcf components is to fork it and do all of those checks and tasks yourself including a full code review of the component as ultimately you are putting 3rd party code in your tenant.
Having such an indicator is also a way to encourage authors to do these tasks and do regular updates.