Build Content Security Policy from a config file
74%
Total Score
caution
Usable with caveats: no commits in the last three months and only one release in the last year.
The package has existed for about 7 years and has 19 releases, but only one release in the last 12 months indicates a slower maintenance pace.
There were no commits and no active maintainers in the last three months, which is a meaningful sign of recently slowed maintenance despite a later repository push being recorded elsewhere.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear, though this is a transparency gap rather than an abandonment signal.
The single workflow was fully analyzed with no dangerous triggers, sinks, or audit findings, but both action references are unpinned, weakening reproducibility and update integrity.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
nette/di Version ^3.2 | — | — |
nette/schema Version ^1.3 | — | — |
spaze/nonce-generator Version ^4.0 | — | — |
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 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.