@lezer/yaml

Repository archiveddanger

The linked repository is archived even though it was pushed recently, so new fixes and maintenance are not dependable. This is a severe adoption risk for a package developers must maintain over time.

Build provenancecaution

No build attestation, trusted publisher, or staged publishing evidence is present. This weakens publication transparency but is not independently severe.

Lifecycle scriptscaution

A prepare script runs during package installation or publication. This is a mild operational consideration, but the provided signals do not show harmful behavior.

Repo commit activitycaution

There were no commits and no active maintainers in the last three months, consistent with the repository's archived state. This reduces confidence that defects will be addressed.

Security policycaution

The repository has no security policy. That leaves vulnerability-reporting expectations unclear, though it does not by itself show abandonment or unsafe code.