Standing service licence-and-snippet-scan-of-new-code-every-month · revised 12 October 2026
Standing service
Have new dependencies and new code scanned for licences and matches every month
Each month the dependencies and code added since the last scan are run through the same named scanners, and your lawyer gets the new lines on the three lists. No legal view is given.
This starts a conversation by email. Nothing is charged, and nothing is monitored, until we have agreed scope, access and terms with you in writing.
The responsibility you hand over
A licence list is a snapshot. New packages and new AI-written code arrive every week, and a new copyleft licence or a copied snippet is easiest to deal with when it is new. Nobody re-runs the scanner unless it is someone's job.
Who it’s for: Lead whose team keeps adding dependencies and AI-written code and who wants the lawyer's lists kept current.
Usually starts when: The first scan is a month old, and AI assistants and new packages have added code since then.
The result: Every month the dependencies and code added since the last scan are run through the same scanners and settings. The new rows on the three lists go to your lawyer, with the commit where each appeared, and the planted snippets and copyleft dependencies are re-run, with any failure or regression flagged.
What stays true, and what we do about it
No response-time guarantee is published for this new service. A date for each monthly report is agreed in writing before it starts.
Hours are agreed in writing before the service starts. It runs once a month and is not staffed round the clock.
What must remain true
- Every added dependency appears once in the monthly inventory with a declared or reported licence or an unknown flag
- Every new match the scanner reports above the agreed length is listed with its source link
- The report gives all planted-test results and flags a missed copyleft dependency, fewer than 12 snippets or any case-level regression
What we watch
- The month-end commit and manifests
- The previous lists and scanner settings
- Your lawyer's decisions on earlier rows
When something happens
Scroll the table sideways to read it all.
| When | What we do |
|---|---|
| A month closes and the new commit is available. | We scan the changes, re-run the planted snippets and copyleft dependencies and send the new rows. |
| You tell us a new package or a large AI-written change landed. | We scan it before the month ends and list the rows. |
| A scanner or its database changes version. | We re-run the planted snippets and copyleft dependencies and say what changed on the lists. |
We do on our own
- Run the same scanners on the month's changes
- Re-run the planted snippets and copyleft dependencies
- Write the note
We ask you first
- Any change of scanner or match length
- Any change to a rule, setting or page in your own systems
- Any wider access than the exports named here
- Contacting your customers or anyone outside your team
We escalate to you when
- A new copyleft or unknown licence appears
- A match above the agreed length appears with a source link
- A planted copyleft dependency is no longer flagged
How you know it held. Each month your team can re-run one list with the commands in the note and get the same rows.
How we keep it true
This service is never finished. Each month's report shows whether the things it watches stayed true, and it continues until you end it.
Scan AI-written code for licence and copied-snippet matches, with a list for your lawyer Job Optional
A named scanner checks one repository's dependencies for licences and its AI-written code for matches to public code. You get a list for your lawyer. We give no legal opinion and no clearance.
Bought separately, each time it is needed; not part of the monthly fee
The one-off job; buy it first if you do not yet have a baseline.
What is included, and what is not
- The monthly list of new rows
- The re-run results for the planted snippets and copyleft dependencies
- The note with counts and commands
Included
- One repository, scanned with the scanners and settings of the one-off job on this site or ones you can show us
- Only changes since the last scan, plus a re-run of the same 15 planted snippets and 5 planted copyleft dependencies
- New dependency licences, new snippet matches and new could-not-judge files, each with its commit
- A monthly note with counts and the commands to re-run
Not included
- A legal opinion or a clearance
- Removing or rewriting code
- Scanning code outside the named repository
- A warranty or an indemnity
- Round-the-clock cover or a response-time guarantee
How we know it’s done
Agreed with you before work starts. Each check produces evidence you keep.
A script compares the complete name-and-resolved-version key sets for added dependencies with the monthly licence list; every added package appears once with a licence or unknown flag. An omitted, duplicate or extra package fails the whole test.
Evidence: The added-dependency and monthly licence-list key sets and the script output.
The report gives the result for every one of the 5 planted copyleft dependencies and 15 planted snippets, and flags any missed dependency, result below 12 snippets or case-level regression first. A missing test result or unflagged failure fails the report test; this frozen suite is a smoke test, not a rate claim.
Evidence: The complete planted-snippet and copyleft-dependency results table.
Your team re-runs one list with the commands in the note and gets the same rows.
Evidence: The commands and your output.
Nothing in your repository has been changed by us.
Evidence: Your repository's audit log for the month.
Sign-off. You read each report and re-run the acceptance checks with the files and steps supplied. A month counts as delivered only when those checks pass.
If it fails. If we cannot do a month because an export is missing or has changed, we say so and do not guess. If the service is not working for you, you can end it at the end of any month.
When it fits, and when we stop
It fits when
- A first scan made under the one-off job or an equivalent baseline list
- Read-only access to one commit a month through a company-controlled route
- A lawyer or adviser who reads the monthly rows
We stop and tell you if
- The lawyer or adviser stops reading the lists for two months
- The baseline list is missing
- Access to new commits is withdrawn
What could go wrong
The service reads exports and reports, so there is nothing to undo. Ending it leaves your systems exactly as they are; you keep every report.
Scroll the table sideways to read it all.
| Risk | How we handle it |
|---|---|
| The monthly rows are read as a clearance. | The note says they are new rows only and that no scanner can show code is free of copied material. |
| A scanner update changes results. | The planted snippets and copyleft dependencies are re-run each month and any change is reported. |
Each report is checked by a separate automated reviewer before hand-over. Your lawyer or adviser reads the new rows and decides what to change. No human supervisor is included unless your agreement names one, and at launch the work is largely automated.
Stays with a person
- Your lawyer or adviser decides what, if anything, to change
- You change your own code
Access we would need
- Read-only access to one commit a month
- A sandbox copy for the scans
Questions
Do you tell me when code is copied?
We list matches the scanner finds and the licence it reports. Your lawyer decides what each one means.
Is a month with no new rows a clearance?
No. It means the scanners found nothing new that month.
Send an enquiry
Send us
- Which repository and which first scan
- Roughly how much code changes a month
- No logins, keys, customer data or payment details in the first enquiry
Later, once you agree
- Read-only code at the month-end commit through the agreed route
- The previous lists, pinned scanner versions and settings, the 15-snippet set and the 5 planted copyleft dependencies
- Your lawyer's decisions on earlier rows, if any
You keep the repository and logins; we receive one agreed commit each month, run scanners on a copy and never change code. Before sharing, the terms name each external scanner or model service used, its country, retention and training status, and when our code copies are deleted.
Email fallback: open your mail app
If website submission is unavailable, review and send the fallback email yourself. An email fallback is not a website receipt. Or write to hello@syntheticindustry.ai with “licence-and-snippet-scan-of-new-code-every-month” as the subject.