Impact

What this has done, counted from the things that did it.

as of 2026-10-30 04:43 UTC

Indicators ingested

1,014

1,246 reports, 7 feeds

Incidents

the incident store

Audit records

20 agent turns

Page renders

—

no page has been rendered since this store was created

Where each number comes from

and what it is not

Indicators and reports: events stored by the scheduled feed poll
Audit ledger: the append-only audit ledger
Page renders: absent — no page has been rendered since this store was created
Uptime: absent — no heartbeat recorded yet — the warm schedule may not be running
Repository: api.github.com/repos/preetraval45/PASHUPATASTRA
Milestones: absent — docs/milestones.json has not been generated

Every figure here is a recount of something that exists for another reason — the feed store, the audit ledger, the warm task's heartbeat, git. Nothing is incremented by this page and kept on its own. Views are renders counted on the server, not people, and nothing authenticates them.

Repository

from the GitHub API, cached hourly

stars: 0
forks: 0
watchers: 0
open issues: 6

Milestones

0 generated from git

docs/milestones.json has not been generated

Each entry is a commit that exists, dated by the commit. Generated rather than written, so this cannot list a milestone that did not land.

Cite this work

from CITATION.cff

permalink: https://pashupatastra.vercel.app
source: https://github.com/preetraval45/PASHUPATASTRA
DOI: no DOI yet — one is minted from a tagged release once the repository carries a licence

BibTeX

@software{raval2026pashupatastra,
  author = {Raval, Preet},
  title = {Pashupatastra: policy-bounded autonomous security operations},
  year = {2026},
  month = {9},
  version = {0.1.0},
  url = {https://pashupatastra.vercel.app},
}

APA

Raval, P. (2026). Pashupatastra: policy-bounded autonomous security operations (Version 0.1.0) [Computer software]. https://pashupatastra.vercel.app

Page renders are counted on the server that rendered them — no cookie, no beacon in your browser, and no identifier per person. Unique visitors would need one, and this site deliberately does not mint one (see how it works). Nothing authenticates the count either: somebody determined could inflate it, which is worth saying rather than presenting the number as audited.