rimba/pinta
Consumer documentation is strong and the release is clearly licensed. Its maintenance history is too new to establish durability, while the workflow uses broad write access and leaves both actions unpinned.
58%
Total Score
75
100
88
75
Health Score Breakdown
Six releases arrived within the same day, with a median interval of about 45 minutes. This shows active initial publishing but provides no longer-term maintenance history.
No commits or active maintainers were recorded over the last three months. Because the package and repository are only hours old, this is chiefly a lack of evidence for durable maintenance rather than proof of abandonment.
Composer build tooling is present, but no security scanning tool was detected. That is a modest repository hygiene gap, not a standalone dependency blocker.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented.
The single workflow was fully analyzed with no high-confidence audit findings, but it grants top-level write permissions and both action references are unpinned. These are workflow hygiene concerns; no untrusted trigger or checkout sink was found.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 BIT Ecosystem |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 rimba/asas Version ^1.3 | — | — |
rimba/jejak Version ^1.3 | — | — |
rimba/orang Version ^1.3 | — | — |
rimba/pihak Version ^1.3 | — | — |
spatie/laravel-permission Version ^7.3 | — | — |
Weekly Downloads
Info
- Last Published
- 2 days ago
- Created
- 2 days 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.