Repository navigation
sp2react 0.1.3
Fixes found in a review of 0.1.2, no runtime dependencies, and signed, verifiable releases. Each fix has a test (tests/test_hardening.py, tests/test_fidelity.py, tests/test_stdlib.py) that fails on 0.1.2.
Security
- Generated app: the catch-all route that serves the front end could return any file on the server (
/..%2fbackend%2f.env,/%2Fetc%2Fhostname). It now serves only files insideFRONTEND_DIST - Generated app:
AUTH_MODEnow defaults toheaderand fails closed (401 without the identity header).devmust be set explicitly, accepts requests from the same machine only, and no longer takes the user from the?as=query parameter. Upgrade note: setAUTH_MODE=devwhen you run the app locally (the generated.env.examplealready does) - Generated app:
/api/screensand/api/specs/{id}now need a signed-in user - Generated app: deleting an item and adding or removing attachments now follow the same role and lock rules as editing it (a locked item answered 204 to
DELETE); attachment names are checked (no/,\,.., leading dots) - Generated app: legacy Content Editor / Script Editor markup is rebuilt from an allow-list (
runtime/sanitize.ts) instead of three regular expressions that<svg/onload>, unquoted and entity-encodedjavascript:links got past - Generated app (
DATA_SOURCE=sharepoint): a user is matched by exact login, not by the first login that contains the text - Agents: file paths proposed by the page, handler and fix agents must be plain relative paths inside the screen's folder; a path with
..could overwritefrontend/vite.config.tsor write outside the output folder. Custom handler names must be identifiers
Fixed
- Columns whose internal name starts with
_or a digit (2nd Approveris_x0032_nd_x0020_Approver,OData__x0032_nd_x0020_Approverin REST) were migrated empty while the reconciliation said every list matched. Fields now record their REST name (rest_name), migration and the SharePoint data source read it, and specs from 0.1.2 work through the same naming rule. Reconciliation now fails when a field is in no exported item - SharePoint throttling (429, 503) and dropped connections are retried with
Retry-After(sharepoint.retries,sharepoint.max_retry_wait). If a list's fields or views, a page's source or web parts, or the SitePages listing still cannot be read,extractfails instead of passing with an empty screen - List pages: the "Title (linked to item)" column (
LinkTitle) showed an empty column headed "LinkTitle"; it is now the Title column linked to the item. The page opens the list's default view with that view's sort order, instead of sorting byID desc - Two pages with the same file name in different libraries (
SitePages/Home.aspx,Pages/Home.aspx) no longer share one screen id: both get their folder in the id - Regenerating the app overwrote files the team had changed, such as
backend/app/auth.py. A changed file is now kept, and the new version is written next to it as<file>.sp2react-new. Apps generated by 0.1.0 to 0.1.2 are recognised, so their unchanged files are still updated - Multi-value lookup columns were edited as a single choice and an edit kept one value; they are now a multi-select list and every value is saved
- Date-and-time columns showed the UTC clock as local time on the edit form, and saved values had no zone. They are now edited in the browser's time zone and stored in UTC (
...Z), as SharePoint returns them; values with an offset are converted by the API - Hyperlink columns lost their description; they are now
{url, description}everywhere (form, list, migration, reconciliation; adescription_columnin the database mapping). Managed metadata was stored as the raw REST object ([object Object]); terms are now{label, term_id}with the label read from the field's hidden note column, shown read-only - List views ignored the view's filter and showed only the first page. The
<Where>of the view is translated to the API filter (comparisons, And/Or, In, Contains, BeginsWith, IsNull,<UserID />,<Today />), a filter that cannot be translated is reported on the page, and the list pages through all items - The list API returned every row when
$topwas not given; like SharePoint it now answers 100 rows by default and at most 5,000 - Wiki pages: their text lives in the page's
WikiFieldcolumn, which was never read, so a wiki page converted to an empty screen. It is now extracted and treated like Content Editor text - A list whose URL name contains a space failed the spec gate (
endpoint path ... must contain only path characters); the API client now also encodes list names in URLs
Added
- Supply chain: hash-locked CI tool sets (
ci/requirements-*.txt), azero-depsjob that installs and runs the package with nothing else installed, weeklypip-auditof every tool set and of the generated app's back end plusnpm auditof its front end, ClusterFuzzLite fuzzing (tests/fuzz: config YAML, spec validation, ASPX/JavaScript analysis, NTLM challenges, the generated API's$filterparser), and an end-to-end workflow that runsdata_source: databaseagainst real MySQL 8.4 and SQL Server 2022 containers - Releases: published from GitHub releases only, with a check that the wheel declares no runtime dependencies, a CycloneDX SBOM, PyPI attestations, and Sigstore-signed wheel, sdist and SBOM on the GitHub release;
verify-release.ymlchecks the signatures and that PyPI serves the same files - Documentation site configuration for Read the Docs (Sphinx + MyST, warnings are errors),
CONTRIBUTING.md,THIRD_PARTY_NOTICES.md;ruffandmypyclean
Changed
- No runtime dependencies.
requests,requests-ntlm,pydanticandPyYAMLare replaced by standard-library code in the package: an HTTP client (transport.py: TLS verification or a CA bundle, proxies fromHTTPS_PROXY/NO_PROXY, redirects checked hop by hop by the network policy), NTLMv2 Windows sign-in with channel binding on HTTPS (ntlm.py, checked against the MS-NLMP test vectors), validated records (model.py) and a YAML reader for the config file (yamlish.py, which refuses anchors, tags, tabs and duplicate keys with a line number).pip install sp2reactinstalls one wheel. Thentlmextra remains, empty - Docs: workflows, event receivers, InfoPath and Power Apps are listed as not detected (they were described as reported); remaining known gaps are listed in 12. Coverage and limitations
Assets: wheel, sdist and a CycloneDX SBOM, each with a Sigstore signature (*.sigstore.json), checked after publishing by verify-release.yml.