opn

Registry deprecationdanger

The entire package is deprecated on npm because it was renamed to `open`, making this release unsuitable for new dependencies despite the source project remaining active.

Release historydanger

The latest registry release is from March 2019, with no releases in the last 12 months, so this package release is obsolete even though its repository is still maintained.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no organizational backing to offset concentrated maintenance.

Repo bus factorcaution

Two contributors were active, but one made 87.5% of recent commits, leaving maintenance concentrated despite the second contributor's activity.

Repo package mentioncaution

The repository name does not match `opn`, and its README does not mention the package, consistent with this package having been renamed and now pointing at the successor project.