readme-inspector

Product development, delivery, and governance

Rules, guidelines, a governance for developing, fixing, maintaining, and delivering readme-inspector.

NPM version GitHub release
The MIT License FOSSA Status NSP Status Known Vulnerabilities
Dependency Status Development Dependency Status
MacOS and Ubuntu build statuses Windows build status Coverage percentage Codacy code quality Maintenance
NPMS score NPM downloads per month

Table of contents

Project dashboard

dashboard Community activity and engagement, as well as project health.

Measure Status/info
Community engagement contributor-count
author<hr>commits-per-year
last-commit<hr>NPM downloads per month
used-by
github-forks
github-stars
github-watchers
Issues issue-opened issues-open
megaphone breaking-change-issues-open
bell feature-issues-open
bug defect-issues-open<hr>issue-closed issues-closed
Pull requests and merges prs-open pull-requests-open
git-merge pull-requests-closed
Product releases, maintenance, and size last-release-date
maintenance
code-size-in-bytes
repository-size

API reference

gear View readme-inspector’s JSDocs.

API design, security, and documentation

radio-tower View readme-inspector’s REST APIs.

Development and testing

beaker Guidelines for developing, building, and testing readme-inspector.

Continuous delivery

squirrel Instructions coming in the next patch or feature release.

Maintenance

repo Instructions coming in the next patch or feature release.

Governance

organization Information coming in the next patch or feature release.

This site is open source. Improve this page.