npati/npati-content-automation
Documentation, tests, release notes, and a security policy make the project easier to assess. It is still a very new package with one release and maintenance concentrated in one apparent owner, while its release workflow has modest pinning and permission hygiene gaps.
68%
Total Score
67
100
88
83
Health Score Breakdown
The repository is owned by an individual user rather than an organization, so the concentrated contributor activity represents a genuine single-owner continuity risk.
The package is only 25 days old and has one release, so its maintenance track record and compatibility history are not yet established.
Two contributors are recorded, but one accounts for 18 of 19 commits, leaving maintenance highly dependent on one apparent owner.
Composer build tooling is present, but no security scanning tool was detected. This is a modest process gap rather than evidence of abandonment.
The single workflow uses top-level write permissions and its one action reference is unpinned, which weakens release reproducibility and token minimization. However, the audit found no dangerous triggers, untrusted checkouts, script injection, or other concrete findings.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 1 month ago
- Created
- 1 month ago
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.