You're pledging to donate if the project hits its minimum goal and gets approved. If not, your funds will be returned.
I am Nicholas Toledo, the sole founder of Toledo Technologies LLC. I maintain EOLkits, a public MIT-licensed project: https://github.com/ntoledo319/EOLkits. I am asking for $1,000 to make six free software-upgrade exercises using synthetic examples and the existing local tools. This is a small educational project, not a claim that I have invented a new scanner or demonstrated broad adoption. This application and the planned implementation use AI assistance; I am responsible for the work released.
Goals and delivery
The exercises would cover Python layer metadata, Node.js runtime lifecycle warnings and Amazon Linux inventory classification. Each would include sample files, a local command, expected results, a plain explanation and a case where the tool cannot give a definite answer. A quiet scan is not proof that a real application is safe to upgrade. I want a learner to be able to inspect an example, reproduce the result and understand that limit.
Deliverables are six exercises, their synthetic inputs, automated expected-output checks, a short guide and a tagged MIT-licensed release. No customer code, AWS account, payment or sales signup would be required. Dependency installation may need internet access. I would target completion within six weeks after funding, checking every documented example from a clean checkout against a pinned scanner revision. The materials would remain publicly reusable, without a paywall. The separate commercial EOLkits report is outside this request.
Budget
The minimum and maximum request are both $1,000: $400 for six exercises and inputs, $200 for expected-output checks, $200 for the guide, and $200 for clean-checkout verification and release packaging. These are prospective deliverable allocations, not incurred expenses or a claimed number of human labor hours. Existing free repository hosting supplies distribution. There is no equipment, advertising or paid cloud deployment in this budget. If costs are funded elsewhere, I would reduce or withdraw this request before accepting overlapping support.
Team and track record
I am the sole person responsible. EOLkits already contains local migration checks and fixture tests, providing a starting point for the lessons. I am not claiming paid customers, classroom trials, outside partners or measured environmental benefits. My studio is pre-revenue. This grant would support the public educational materials, not unrestricted company spending.
Risks and failure
The examples could be harder to reproduce than expected, upstream tool or runtime changes could make a lesson stale, and the materials might attract little use. I would keep the first release narrow, pin the versions, test the documented commands, publish limitations and report what was actually completed. If I could not finish the proposed work, I would notify Manifund and follow its rules for unused funds and any proposed change. Reproducibility is the completion test; adoption or migration safety is not guaranteed.
Other funding
No outside funding has been received or promised. Awesome Boston and Awesome Ottawa have pending alternative requests for this same educational scope. An Emergent Ventures form for the same work is prepared but not yet confirmed submitted. Sequoia, EVM Capital and Alya have pending EOLkits maintenance-related requests. These are not awards. I would disclose any offers, reconcile overlapping deliverables before accepting funds and never fund the same costs twice. I would post a concise public completion and spending update. This project includes no lobbying or political activity.