drosera 0.1.0__tar.gz

drosera-0.1.0/CHANGELOG.md

@@ -0,0 +1,75 @@
+# Changelog
+
+All notable changes to Drosera are recorded here. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Fixed
+
+- `FileWatcher` missed a canary modification that happened less than a
+  millisecond after the previous poll. It compared float-seconds timestamps
+  with a 0.001 tolerance, and on a fast filesystem the real gap is smaller than
+  that. Comparisons now use integer nanosecond timestamps, which need no
+  tolerance at all. It also compares file size, because Windows timestamps
+  advance only on the ~15.6ms system clock tick and two writes inside one tick
+  share an mtime. The watcher now baselines from a live stat when watching
+  starts, and reports separately when a file was already modified before then.
+
+### Added
+
+- A public playground under `web/`: a Vercel-deployable page that scores four
+  request traces with the real engine, and can score the visitor's own browser.
+  Guarded by `tests/test_playground.py` so the demo cannot drift from the
+  library it is demonstrating.
+
+### Changed
+
+- Packaging modernised for PyPI: PEP 639 SPDX licence expression with explicit
+  licence files, a `MANIFEST.in` so the sdist carries tests and docs, and
+  absolute documentation links in the README (relative ones 404 on PyPI).
+- Release is automated via PyPI Trusted Publishing on a `v*` tag. No API token
+  exists in the repository or its secrets.
+
+- `Verdict`, `Category` and `Action` now subclass `enum.StrEnum` instead of
+  `(str, Enum)`. Behaviour is unchanged for `.value`, comparison and JSON
+  serialisation.
+- Pinned `ruff>=0.16,<0.17` for development. An open-ended range meant a new
+  linter release could fail CI on an unrelated commit.
+
+## [0.1.0] - 2026-09-05
+
+First release.
+
+### Added
+
+- **Detection engine** with 30 signals across five categories, scored on three
+  independent axes (`automation`, `agency`, `hostility`). An `agent` verdict
+  requires comprehension evidence or explicit self-identification; traffic shape
+  alone can never produce one.
+- **Lure layer** with three bait channels: raw-markup (HTML comment plus hidden
+  block), rendered (visible `/llms.txt` pointer), and convention (`robots.txt`,
+  `llms.txt`, both served per-session with an HMAC-signed ticket).
+- **`assert_inert` guardrail**, enforced on every piece of bait including
+  operator-supplied templates, rejecting text that coerces an agent rather than
+  inviting it.
+- **Tarpit**: an endless, deterministic maze seeded from each page's own URL,
+  marked `noindex, nofollow, noarchive`, with optional slow-drip delivery and a
+  per-session byte budget.
+- **Derail**: terminal responses that close an agent's task branch cleanly.
+- **Canary credentials** for eight file kinds, inert and HMAC self-verifying,
+  with use-detection (hard evidence) and access-time watching (soft hint) kept
+  visibly separate.
+- **ASGI and WSGI middleware**, plus a zero-dependency standalone honeypot
+  server built on `http.server`.
+- **Telemetry sinks**: JSONL, SQLite, webhook, stderr, with optional IP
+  redaction. Sinks never raise into the request path.
+- **Export formats**: terminal summary, CSV, JSON, IOC, and STIX 2.1 — each row
+  carrying a confidence class derived from evidence type rather than score.
+- **CLI**: `serve`, `demo`, `replay`, `report`, `signals`, `canary`, `init`,
+  `doctor`.
+- Zero runtime dependencies, enforced in CI.
+
+[Unreleased]: https://github.com/rod-trent/Drosera/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/rod-trent/Drosera/releases/tag/v0.1.0

drosera-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,59 @@
+# Code of Conduct
+
+## Our pledge
+
+We as members, contributors, and maintainers pledge to make participation in the
+Drosera project a harassment-free experience for everyone, regardless of age,
+body size, visible or invisible disability, ethnicity, sex characteristics,
+gender identity and expression, level of experience, education, socio-economic
+status, nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our standards
+
+Examples of behaviour that contributes to a positive environment:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility, apologising to those affected by our mistakes, and
+  learning from the experience
+- Focusing on what is best for the community
+
+Examples of unacceptable behaviour:
+
+- Sexualised language or imagery, and sexual attention or advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Project-specific expectations
+
+Drosera is security tooling. Two additional expectations follow from that:
+
+- **Do not use this project's spaces to coordinate offensive use.** Issues, pull
+  requests and discussions are for defending systems you operate. Requests to
+  turn the lure into a weapon against third-party agents, or to make the tarpit
+  emit disinformation, are off-topic and will be closed. See
+  [docs/ethics.md](docs/ethics.md).
+- **Report vulnerabilities privately.** See [SECURITY.md](SECURITY.md).
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behaviour may be
+reported to the project maintainers through a private [security
+advisory](https://github.com/rod-trent/Drosera/security/advisories/new) or by
+contacting the repository owner directly. All complaints will be reviewed and
+investigated promptly and fairly.
+
+Maintainers are obligated to respect the privacy and security of the reporter of
+any incident, and have the right to remove, edit, or reject contributions that
+are not aligned with this Code of Conduct.
+
+## Attribution
+
+Adapted from the [Contributor Covenant](https://www.contributor-covenant.org),
+version 2.1.

drosera-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,110 @@
+# Contributing to Drosera
+
+Thanks for looking. This is a defensive security project, and the bar for
+changes reflects that.
+
+## Setup
+
+```bash
+git clone https://github.com/rod-trent/Drosera
+cd Drosera
+python -m venv .venv && . .venv/bin/activate   # Windows: .venv\Scripts\activate
+pip install -e ".[dev]"
+pytest && ruff check .
+```
+
+Python 3.11+ (we use `tomllib`). No runtime dependencies — see below.
+
+## What is most useful
+
+**False-positive reports, above everything else.** If Drosera called you, your
+users, or a legitimate client an agent, that is the most valuable issue you can
+file. Include the request shape (headers, paths, timing) and what actually made
+the requests. A false positive on a real person is the expensive error, and it
+is the one we cannot find without you.
+
+**Agent behaviour in the wild.** How does framework X consume a page? Does it
+see `display:none` blocks? Does it read `llms.txt`? Does it follow prose
+instructions? Concrete observations turn into signals.
+
+**New signals.** See below.
+
+**Documentation that corrects something.** If a doc claims a property the code
+does not have, that is a bug.
+
+## Adding a detection signal
+
+1. Add a `SignalDef` to the right category in `src/drosera/detect/rules.py`.
+2. Add a detector in `src/drosera/detect/signals.py` that yields it.
+3. Regenerate the reference: `python docs/_gen_signals.py`.
+4. Add tests — at minimum, one that fires it and one that proves a plausible
+   human does not.
+
+### Choosing a weight
+
+Before picking a number, ask: **what else produces this exact observation?**
+
+If a person using a text browser, a screen reader, a corporate proxy, a privacy
+extension, or a slow connection could trip it, it belongs in the corroborating
+tier (0.30–0.55) or below. Most signals belong there.
+
+The comprehension tier (0.90+) is reserved for evidence that the client read
+prose and acted on its meaning. Not "behaved like software" — *understood
+language*. If you cannot explain why a regex-driven scraper is incapable of
+producing the observation, it is not a comprehension signal.
+
+### The rule that is not negotiable
+
+**Only comprehension signals and `id.declared_agent` may feed the LLM-agency
+axis.** Behavioural and identity signals feed `automation` only.
+
+Traffic shape cannot distinguish a language model from a shell script. A change
+that lets behaviour produce an `agent` verdict will be declined, however good the
+score looks on a sample — it is inventing a claim the evidence does not support,
+and everything downstream inherits the error.
+`test_behavioural_signals_alone_never_reach_agent` guards this.
+
+## Lure text
+
+All bait passes through `drosera.lure.nectar.assert_inert`, which rejects text
+that coerces rather than invites. If your new lure trips it, the check is
+probably right — read [docs/ethics.md](docs/ethics.md).
+
+Changes that weaken or bypass `assert_inert` will not be merged. Drosera detects
+prompt injection against third-party agents; it does not perform it.
+
+## Zero dependencies
+
+Drosera has no runtime dependencies and that is deliberate: it can be dropped
+onto an isolated host with nothing but Python, it has no supply chain of its own,
+and an upstream release cannot break a deployed honeypot.
+
+Test/lint tooling under `[dev]` is fine. A runtime dependency needs a strong
+argument in the PR description.
+
+## Style
+
+- Ruff for lint and import order (`ruff check .`). Line length 100.
+- Type hints on public functions.
+- Comments explain **why**, not what. If a weight, threshold, or design choice is
+  non-obvious, the reasoning belongs next to it — most of this codebase's
+  comments are load-bearing for exactly that reason.
+- Telemetry and lure code must never raise into the request path. A honeypot
+  that errors has announced itself.
+
+## Tests
+
+`pytest` must pass. New behaviour needs a test. Tests that pin a *guarantee*
+(never trap a human, never claim LLM from behaviour, never overwrite a real
+`.env`, canary keys are non-functional) are more valuable than tests that pin an
+implementation detail.
+
+If you change a test to make it pass, say why in the PR. Sometimes the assertion
+was wrong — that is legitimate, and it should be visible.
+
+## Security issues
+
+Do not open a public issue. See [SECURITY.md](SECURITY.md).
+
+Specifically in scope: a way to make Drosera harm an agent's operator, or a lure
+that slips past `assert_inert`. Those are vulnerabilities in this project.

drosera-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Rod Trent and Drosera contributors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

drosera-0.1.0/MANIFEST.in

@@ -0,0 +1,8 @@
+# Ship a source distribution a downstream packager can actually verify:
+# tests included so `pytest` works from an unpacked sdist.
+include CHANGELOG.md CONTRIBUTING.md SECURITY.md CODE_OF_CONDUCT.md
+recursive-include tests *.py
+recursive-include docs *.md *.py
+recursive-include examples *.py *.md
+prune .github
+global-exclude __pycache__ *.py[cod] .DS_Store

drosera-0.1.0/NOTICE

@@ -0,0 +1,5 @@
+Drosera
+Copyright 2026 Rod Trent and Drosera contributors
+
+This product includes software developed for defensive security research.
+Licensed under the Apache License, Version 2.0.