@samverschueren/stream-to-observable

Release historydanger

Only two releases exist, with no releases in the last 12 months and the latest published over six years ago. This substantially increases the risk that compatibility issues or defects will not be addressed.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is the main reason to expect limited ongoing support.

Build provenancecaution

No build attestation or trusted-publisher provenance is present, reducing publication transparency. This is a supply-chain transparency gap but not by itself evidence that the package is unsafe.

Maintainerscaution

Only one registry account has publish access. That is a limited operational bus factor for a user-owned project, although access records alone do not establish actual maintenance activity.

Repo toolingcaution

No build tools or security-scanning tools were detected. For this small JavaScript package this is a modest transparency and maintenance concern, though the repository remains simple and inspectable.