Package Health/guilhermecfviana/sped-nfe

guilhermecfviana/sped-nfe

The package is well documented, licensed, tested in its repository, and published without install-time scripts. The absence of security scanning and unpinned workflow actions add hygiene risk, while the long publication silence limits confidence in ongoing support.

Latest v5.1.18

Packagist

46%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the release history showing no release for over two years. This is a material maintenance and abandonment concern.

Project backing

The registry namespace and repository are owned by the same individual account, so the package does not show organization backing that would compensate for its thin recent activity.

Release history

The package has 49 releases but none in the last 12 months, and its latest release was published over two years ago. This strongly reduces confidence that current regulatory or dependency changes will be addressed.

Repo tooling

The repository uses Composer, but no security scanning tools were detected. The build setup is present, though security-process transparency is limited.

Security policy

The repository has no security policy, leaving no documented process for reporting or coordinating vulnerability fixes. This is a transparency gap, especially for software handling electronic invoices and certificates.