fnl-open-source-review
Open source review
A read-only review: it finds and reports, it does not publish. Fixes, history rewrites, visibility changes and releases each need the owner's explicit authority. After a repository is public, run it again before each MINOR release and whenever SECURITY.md, CI or the repository settings change; a patch release does not need one.
1. Fix the scope
Name the repository, the exact commit, and what will become public: the working tree, the full git history, release archives, or a packaged plugin. History counts unless the owner will publish a fresh history; say which.
Done when the scope line is written in the report.
2. Run every check
Mark each item PASS, FAIL, N/A (with why) or BLOCKED (with what is missing), and attach evidence: the command and its output, or the file and line. A tool that is not installed is BLOCKED, not PASS, unless the check names a fallback; a fallback result names the method it used.
License
- A
LICENSEfile at the root, and the same SPDX id in every manifest (package.json, plugin manifests,pyproject.toml). - Notices for vendored or copied third-party code, with their original licenses kept.
- Dependency licenses are compatible with the project license.