fleet-sensor-baseline 0.1.0__tar.gz

fleet_sensor_baseline-0.1.0/.githooks/commit-msg

@@ -0,0 +1,25 @@
+#!/bin/sh
+# Check the commit message before it becomes permanent.
+#
+# Activated by the same setting as the pre-commit hook:
+#     git config core.hooksPath .githooks
+#
+# A message is the one published surface that can never be corrected.
+#
+# **This file used to claim it ran the hygiene rules over the message, and it did
+# not.** It ran only `commit_msg_check.py`, which checks the subject length and
+# insists a three-digit number carries a measurement basis -- both worth having,
+# neither about publication. So the comment described the property that would have
+# stopped an internal repository nickname reaching four public commit messages,
+# while the code did something else entirely. Nothing checked the claim, because it
+# was a claim in a comment.
+#
+# This runs the publication vocabulary over the message: must this text never be
+# published? It is the one surface that cannot be undone after a push.
+#
+# To commit past it knowingly:   git commit --no-verify
+# Note that --no-verify also disables the pre-commit hygiene sweep.
+set -e
+ROOT="$(git rev-parse --show-toplevel)"
+
+exec python3 "$ROOT/tools/hygiene_check.py" --message "$1"

fleet_sensor_baseline-0.1.0/.githooks/pre-commit

@@ -0,0 +1,16 @@
+#!/bin/sh
+# Refuse a commit carrying something that should not be published.
+#
+# Activate once per clone:   git config core.hooksPath .githooks
+#
+# Versioned deliberately. A hook that lives only in .git/hooks exists on one
+# machine, is invisible in review, and is absent from every fresh clone -- which
+# for a repository authored in public means the safety check is missing exactly
+# when a new contributor needs it most.
+#
+# The companion commit-msg hook runs the SAME vocabulary over the message, which
+# is the one published surface that cannot be corrected after a push.
+#
+# To commit past it knowingly:   git commit --no-verify
+set -e
+exec python3 "$(git rev-parse --show-toplevel)/tools/hygiene_check.py"

fleet_sensor_baseline-0.1.0/.github/workflows/checks.yml

@@ -0,0 +1,101 @@
+# The suite twice, because the two lanes answer different questions.
+#
+# The dependency-free lane is what a jump host gets: ingest, baseline, outliers,
+# drift, verdict and validate, on the standard library alone. If that lane needs
+# something installed, the claim in the README stopped being true.
+#
+# The referee lane unskips the seam. Those 14 are the only tests that can notice
+# the upstream format string changing, `validate-walk` refusing what `capture`
+# wrote, or the printed digest ceasing to describe the file -- and none of them
+# can run without the tool. **A suite that only ever ran the first lane would be
+# green on a broken seam**, which is exactly what the skips say in prose.
+#
+# The referee is pinned as a range. Any 0.1.x release lands here without this
+# repository changing, which is precisely the seam the second lane can notice.
+
+name: checks
+
+on:
+  push:
+  pull_request:
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  checks:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          # Tags are what `test_a_tag_and_the_tree_do_not_disagree` reads, and
+          # `fetch-depth: 1` fetches none of them. The check answers *cannot
+          # tell* in that case rather than *no tags*, which is honest and is
+          # also not the answer we came for.
+          fetch-depth: 0
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+
+      - name: Install, dependency-free
+        run: |
+          set -euo pipefail
+          python3 -m pip install --quiet --upgrade pip
+          python3 -m pip install --quiet -e ".[dev]"
+
+      - name: The dependency-free lane
+        # Expected: some tests skip, and every one of them says why. A skip here
+        # is the seam being unchecked, not the seam being fine.
+        run: python3 -m pytest tests/ -q -rs
+
+      - name: Nothing was installed behind our back
+        # The claim in the README and in NOTICE is that the core imports no
+        # third-party package. This is the check for it -- an import that crept
+        # into `store.py` would still pass the lane above on a runner where the
+        # referee happened to be present.
+        run: |
+          set -euo pipefail
+          python3 -c "
+          import importlib, sys
+          sys.path.insert(0, 'src')
+          assert 'bmc_sensor_audit' not in sys.modules
+          for name in ('store', 'formats', 'baseline', 'outliers', 'drift',
+                       'verdict', 'walk', 'report', 'exits', 'cli'):
+              importlib.import_module('fleet_sensor_baseline.' + name)
+          leaked = sorted(m for m in sys.modules if m.startswith('bmc_sensor_audit'))
+          assert not leaked, f'the core pulled in {leaked}'
+          print('  core imports nothing from the referee')
+          "
+
+      - name: Install the referee
+        run: |
+          set -euo pipefail
+          python3 -m pip install --quiet -e ".[collect,dev]"
+          python3 -m pip show bmc-sensor-audit | sed -n 's/^Version: /  referee /p'
+
+      - name: The referee lane -- the seam, unskipped
+        run: python3 -m pytest tests/ -q
+
+      - name: The seam lane is not empty
+        # Non-vacuity. If the marker were dropped from every test, the step
+        # above would still be green and would be testing nothing upstream.
+        run: |
+          set -euo pipefail
+          collected=$(python3 -m pytest tests/ -m seam --collect-only -q \
+            | sed -n 's#^\([0-9]\+\)/[0-9]\+ tests collected.*#\1#p')
+          echo "  seam tests: ${collected:-0}"
+          test "${collected:-0}" -gt 0
+
+      - name: The publication vocabulary, over the tree
+        run: python3 tools/hygiene_check.py --all
+
+      - name: A mock rack, end to end
+        # 0.3's exit criterion, stated as a command: a verdict produced from
+        # nothing but BMC endpoints. It runs against fake machines, which is the
+        # only tier available without hardware -- and it is the tier the exit
+        # criterion names.
+        run: |
+          set -euo pipefail
+          python3 -m pytest tests/test_seam.py::TestTheCollectorAgainstAMockRack -q

fleet_sensor_baseline-0.1.0/.gitignore

@@ -0,0 +1,15 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+build/
+dist/
+*.egg-info/
+.venv/
+venv/
+
+# Walks recorded from a real machine. A Redfish walk carries serial numbers, asset
+# tags and MAC addresses, so a capture is a fleet inventory disclosure. Scenario
+# runs write walks to a temporary directory for exactly this reason; anything
+# landing here was put here deliberately and should be looked at before committing.
+walks/
+*.capture.json

fleet_sensor_baseline-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,60 @@
+# Contributing
+
+## Turn the hooks on
+
+A fresh clone gets the hook files and does not get them activated — `core.hooksPath`
+is per-clone and git will not set it for you. One command:
+
+```
+git config core.hooksPath .githooks
+```
+
+That wires two checks:
+
+- **`pre-commit`** runs the publication vocabulary over the staged files.
+- **`commit-msg`** runs the same vocabulary over the message.
+
+Both matter, and the second is the one that was missing across four repositories
+in this family until a nickname reached their public commit messages. **A commit
+message is the one published surface that cannot be corrected after a push** — a
+force-push supersedes a commit, it does not remove it; the old object still
+resolves by hash.
+
+`git commit --no-verify` skips both. It is there for when you know why.
+
+## The rules that are not negotiable
+
+**Nothing in `src/` may import `bmc_sensor_audit`**, with exactly one exception:
+`collect/backends/mock.py`, which imports `MockBMC` because that is a fake
+*machine* rather than a fake referee. `tests/test_boundary.py` asserts both
+halves — the absence everywhere else, and the presence there, because without
+the second the first would pass by finding nothing.
+
+**A number in prose has an owner.** Every count the README states is derived by
+`tests/test_readme_counts.py` from the thing it describes. If you add a test,
+that file goes red until the README agrees. That is the point.
+
+**A guard proves it can refuse.** Every validator, every comparison, every
+threshold here has a test showing it saying no to something. A check that has
+never refused anything is not evidence.
+
+**Could-not-check is not found-nothing.** Exit `2` when the answer is unknown,
+`1` when something was found, and say which in prose. A skip explains itself.
+
+## Running the tests
+
+```
+python3 -m pytest tests/ -q                 # 185 passed, 15 skipped
+pip install -e ".[collect]" && pytest -q    # 199 passed, 1 skipped
+```
+
+The 14 that skip without `bmc-sensor-audit` carry the `seam` marker and exercise
+the upstream boundary. The 15th skips while this repository has no tags.
+
+Run `python3 tools/hygiene_check.py --all` before opening anything.
+
+## Style
+
+Docstrings say **why**, and name the specific defect a guard exists for. A
+comment that restates the code is noise; a comment recording the mistake that
+made the line necessary is the only durable form of that knowledge.

fleet_sensor_baseline-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 [yyyy] [name of copyright owner]
+
+   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.

fleet_sensor_baseline-0.1.0/NOTICE

@@ -0,0 +1,38 @@
+fleet-sensor-baseline
+Copyright 2026 James Sheen
+
+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.
+
+DEPENDENCIES
+
+None at runtime. Ingest, baseline, outliers, drift, verdict and validate are
+JSON and arithmetic, built on the standard library so the vertical and
+horizontal axes run on a bring-up bench, a CI runner or a jump host with nothing
+provisioned first.
+
+Two optional, neither of them imported for a verdict:
+
+    bmc-sensor-audit      Apache-2.0   the referee, run as a subprocess by
+                                       `collect` and read through its exit code,
+                                       its stdout and the files it writes -- see
+                                       collect/backends/subprocess_backend.py,
+                                       and the test that parses this package's
+                                       imports to keep it that way
+    pytest                MIT          tests only; not installed by a plain
+                                       `pip install fleet-sensor-baseline`
+
+One module imports `bmc-sensor-audit` directly and is named here rather than
+left to be discovered: `collect/backends/mock.py` uses its `MockBMC` to stand up
+fake machines for the collector's own tests. That is a fake MACHINE, not the
+referee, and the distinction is the architectural boundary of this package.
+
+Licences read from each distribution's own metadata, not from a list written
+somewhere else and copied.