flowpack/decoupledcontentstore
Tests, a substantial README, and GitHub release notes improve confidence, with organizational ownership supporting continuity. Maintenance currently rests on one contributor, and all six workflow actions are unpinned; pin this version while watching maintainer coverage.
78%
Total Score
83
94
67
Health Score Breakdown
All 22 recent commits came from one contributor, leaving maintenance dependent on a single active person despite the organization-owned repository.
Composer build tooling is present, but no security scanning tooling was detected, leaving a modest transparency gap.
The repository has no security policy, so the process for reporting and handling vulnerabilities is not documented.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injections, or audit findings, but all 6 action references are unpinned and the workflow has no top-level permissions block.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 neos/neos Version ^8.0 | — | — |
flowpack/prunner Version * | — | — |
albertofem/rsync-lib Version ~1.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 days ago
- Created
- 4 years 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.