blinkpy

A Python library for the Blink Camera system

Runs with mockssource: GitHubPythonMITcommit c36646ea0c83

Python, MIT licensed. The project labels itself: api, blink, camera, hacktoberfest, home automation and security camera.

blinkpy runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

blinkpy 0.26.0b0 installed in a Python 3.12 virtual environment; all 249 tests pass using mocked HTTP responses

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
817
forks
172
open issues
34
watchers
31
size
3 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
under a minute
Cold machine to finish
19 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
pytest tests/ exited 0, 249 passed, 2 warnings
Model tokens used
202,211
Exact commit tested
c36646ea0c83
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

    File "/usr/lib/python3.12/unittest/mock.py", line 1138, in _mock_call
      return self._execute_mock_call(*args, **kwargs)
    def __init__(self, name, parent):
  Enable tracemalloc to get traceback where the object was allocated.
  See https://docs.pytest.org/en/stable/how-to/capture-warnings.html#resource-warnings for more inf…
-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
249 passed, 2 warnings in 39.33s
EXIT=0
Installation was smooth — created a venv, installed the package and test deps with no errors. The f…
tokens used
202,211
Installation was smooth — created a venv, installed the package and test deps with no errors. The f…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 0.3 minutes, faster than the median of the 61 comparable projects Argusic has measured.
  • Nothing broke on the way: zero errors between clone and running.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 62 api projects Argusic has installed and timed, blinkpy was the 4th fastest to reach a running state, and 37 of 62 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.06

Topics (from GitHub)

apiblinkcamerahacktoberfesthome-automationsecurity-camera

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/blinkpy.svg)](https://argusic.com/subject/blinkpy)

Questions

Does blinkpy run?
blinkpy runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test blinkpy?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c36646ea0c83. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test blinkpy?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does blinkpy take to install?
0.3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does blinkpy need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing blinkpy?
Nothing did, in the recorded run: zero errors between clone and running.
How does blinkpy compare with the alternatives?
Of the 62 api projects Argusic has installed and timed, blinkpy was the 4th fastest to reach a running state, and 37 of 62 reached one at all.
Where is the evidence for blinkpy?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion