@mischnic/json-sourcemap

Clear documentation, bundled types, repository tests, and a small runtime dependency set reduce adoption friction. The long inactivity makes future fixes and compatibility work uncertain.

Latest 0.1.1

NPM

57%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository had no commits and no active maintainers in the last three months; together with the old last push, this indicates inactivity rather than active maintenance.

Project backing

The registry namespace and repository are owned by the same individual account, which supports package identity but does not provide organizational maintenance capacity.

Release history

Only two releases have been published, with no releases in the last three years and a median interval of about 528 days, indicating a very slow maintenance cadence.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and none remain open. This is consistent with a small, quiet project but provides no evidence of ongoing support.

Repo tooling

The repository uses TypeScript, Parcel, and npm scripts, showing a defined build process, but no security-scanning tooling was detected.