lopescte/pncp-api
Clear licensing, a usable README, release notes, and a small dependency surface make adoption straightforward. The workflow has limited hygiene concerns, but there is no sign of abandonment or unsafe release behavior.
82%
Total Score
75
100
94
75
Health Score Breakdown
Two contributors were active in the last 3 months, although the leading contributor made two-thirds of commits. The second contributor is an automated release bot, so human maintenance remains concentrated.
Composer build tooling is present, but no security-scanning tool was detected. This is a process gap, not evidence of a known defect.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities.
The single workflow was fully analyzed and has no untrusted checkout or script-injection findings, but both action references are unpinned, the workflow grants top-level write access, and it high-confidence reports an ad hoc package install.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Marcelo Lopes |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 guzzlehttp/guzzle Version ^7.8 | — | — |
justinrainbow/json-schema Version ^5.2 | — | — |
Weekly Downloads
Info
- Last Published
- 3 months ago
- Created
- 1 year 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.