Skip to content
Menu

Pranith-Jain.github.io

No narrative yet

Is this your project? Claim and verify →

What HEY knows

Building
Shipping consistentlyShipping: 5 meaningful events in 30 days; latest ship today. Evidence Source

Build Momentum 53How it is measured

Latest ship
Code changes this week (since Mon 26 Oct) · 20 commits
This change
Code changes, read from the team’s GitHub · not a deployment
What it names
0 of 10 commits HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it to the week of 2026-10-28; HEY first knew on 2026-10-26.
Not known
  • No source HEY holds names what this change does.
  • HEY could not read whether every commit of this week changed code.
  • HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts Pranith-Jain.github.io on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

No account? Email me Pranith-Jain.github.io’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 5 meaningful events in the last 30 days, the newest 2026-10-28.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 26 Oct) · 20 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 34 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 49 commits+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source2 registered sources, 1 of them context only.ReadRecordsCode changes this week (since Mon 26 Oct) · 20 commitsCode changes, week of 2026-10-19 – 2026-10-25 · 34 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 49 commits+3 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes this week (since Mon 26 Oct) · 20 commits

Code activitySource linked

Why it matters: One of 5 meaningful events in the last 30 days: building continued, not a one-off.

What changed, in the repository’s own words:

3 active days in pranith-jain/pranith-jain.github.io.

HEY could not tell what 2 commits changed this week. This week HEY looked inside 10 commits to see what changed: 8 documentation or maintenance only, 2 could not be classified. 24 automated commits (bot accounts or a repeating scripted message) not counted.

Record ship:a35a9faa… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗ (opens in a new tab)

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 3 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Pranith-Jain.github.io — as of 28 Oct

Is Pranith-Jain.github.io still being built?
DerivedShipping: 5 meaningful events in 30 days; latest ship today. Evidence
What did Pranith-Jain.github.io ship last?
FactCode changes this week (since Mon 26 Oct) · 20 commits — Code activity, today. Evidence
What does HEY not know about Pranith-Jain.github.io?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-10-19 – 2026-10-25 · 34 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in pranith-jain/pranith-jain.github.io.

    How HEY read this week

    This week HEY looked inside 5 of 22 commits to see what changed: 3 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 100 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · 34 commits (opens in a new tab)

  2. Code changes, week of 2026-10-12 – 2026-10-18 · 49 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    5 active days in pranith-jain/pranith-jain.github.io.

    How HEY read this week

    This week HEY looked inside 4 of 49 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 71 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 49 commits (opens in a new tab)

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 47 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in pranith-jain/pranith-jain.github.io.

    How HEY read this week

    This week HEY looked inside 6 of 47 commits to see what changed: 3 changed code, 3 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 61 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 47 commits (opens in a new tab)

  4. Code changes, week of 2026-09-28 – 2026-10-04 · 69 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in pranith-jain/pranith-jain.github.io.

    How HEY read this week

    This week HEY looked inside 5 of 69 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count. 70 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 69 commits (opens in a new tab)

  5. Code changes, week of 2026-09-21 – 2026-09-27 · at least 28 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    at least 7 active days in pranith-jain/pranith-jain.github.io since 2026-09-21; the count stops at the newest 100 commits listed.

    How HEY read this week

    This week HEY looked inside 1 of 16 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 58 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · at least 28 commits (opens in a new tab)

  6. Code changes, week of 2026-09-14 – 2026-09-20 · at least 33 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    7 active days in pranith-jain/pranith-jain.github.io.

    How HEY read this week

    This week HEY looked inside 3 of 21 commits to see what changed: 1 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there. 51 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 33 commits (opens in a new tab)

  7. Code changes, week of 2026-09-07 – 2026-09-13 · at least 29 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in Pranith-Jain/Pranith-Jain.github.io.

    How HEY read this week

    This week HEY looked inside 3 of 29 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 49 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 29 commits (opens in a new tab)

  8. Code changes, week of 2026-08-31 – 2026-09-06

    Code activitySource linked

    11 active days in Pranith-Jain/Pranith-Jain.github.io.

    Automated commits only — not counted as building. 49 automated commits (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 (opens in a new tab)

What changed

9 changes on HEY’s record for Pranith-Jain.github.io: 9 weeks of code pushed.

All 9 changes for Pranith-Jain.github.io →

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 53d ago.

Building

  • Building activityMeasuredRead 4m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 1d ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources

  • Repository
    https://github.com/Pranith-Jain/dfir-threat-intel-platformContext onlyContext only because HEY found this repository by its owner alone and nothing the project controls ties it to the project; it counts once a moderator accepts it, or once the project’s verified owner adds it and a GitHub claim names it, it names the token’s contract, it carries a Robinhood Chain dedication HEY matched to this project, or its homepage is the project’s own site (one the owner did not type in).
  • Repository
    https://github.com/Pranith-Jain/Pranith-Jain.github.ioOfficial