Skip to content
Menu

Denis101Ka

Perps

Is this your project? Claim and verify →

Open tooling for Predly: recompute every market price, read Robinhood Chain yourself, run the board offline.

What HEY knows

Building
Quiet for 43 daysQuiet: 0 meaningful events in 30 days; latest ship 43 days ago. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-09-07 – 2026-09-13 · at least 10 commits · · Code activity

Why it matters: The first week of code changes HEY has recorded for this project.

Latest change
Derived25 days ago: Code changes, week of 2026-09-28 – 2026-10-04. Not counted as building. Evidence Source

Maintenance only, read from the team’s GitHub · not a new capability

What this change is
What it names
Maintenance only, not a new capability: 0 of 0 commits HEY read were documentation, dependency or maintenance changes, and none changed code.
Stage
Maintenance is not a new capability, and code is not a deployment.
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-01; HEY first knew on 2026-09-28.
Not known
  • No source HEY holds names what this change does.
  • 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 Denis101Ka 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 Denis101Ka’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
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.

HEY can answer 8 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
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-09-13.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · at least 10 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · at least 10 commitssource:47a93483-1a14-41fe-9ea8-8ed56057bb7dsource:ba7c072a-6226-4ca2-b96b-856e03a2249f+1 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
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-07 – 2026-09-13 · at least 10 commits denis101ka/predly-tools

Code activitySource linked

What changed, in the repository’s own words:

2 active days in denis101ka/predly-tools.

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

Record ship:a8a8e66e… · 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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about Denis101Ka — as of 26 Oct

Is Denis101Ka still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship 43 days ago. Evidence
What did Denis101Ka ship last?
FactCode changes, week of 2026-09-07 – 2026-09-13 · at least 10 commits — Code activity, 43 days ago. Evidence
What does HEY not know about Denis101Ka?
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs. 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. 6 code weeks of maintenance or automation only — not counted as building

    Show the 6 weeks

    1. Code changes, week of 2026-09-28 – 2026-10-04 · 16 commits denis101ka/predly-tools

      Code activitySource linked

      4 active days in denis101ka/predly-tools.

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

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

    2. Code changes, week of 2026-09-28 – 2026-10-04 · 16 commits denis101ka/predly

      Code activitySource linked

      4 active days in denis101ka/predly.

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

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

    3. Code changes, week of 2026-09-21 – 2026-09-27 · 28 commits denis101ka/predly-tools

      Code activitySource linked

      7 active days in denis101ka/predly-tools.

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

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

    4. Code changes, week of 2026-09-21 – 2026-09-27 · 28 commits denis101ka/predly

      Code activitySource linked

      7 active days in denis101ka/predly.

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

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

    5. Code changes, week of 2026-09-14 – 2026-09-20 · at least 28 commits denis101ka/predly-tools

      Code activitySource linked

      7 active days in denis101ka/predly-tools.

      Automated commits only — not counted as building. 28 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 28 commits (opens in a new tab)

    6. Code changes, week of 2026-09-14 – 2026-09-20 · at least 27 commits denis101ka/predly

      Code activitySource linked

      7 active days in denis101ka/predly.

      Automated commits only — not counted as building. 28 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 27 commits (opens in a new tab)

  2. Code changes, week of 2026-09-07 – 2026-09-13 · 10 commits denis101ka/predly

    Code activitySource linked

    What changed, in the repository’s own words:

    2 active days in denis101ka/predly.

    How HEY read this week

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

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

What changed

9 changes on HEY’s record for Denis101Ka: 1 build pace change · 8 weeks of code pushed.

All 9 changes for Denis101Ka →

The full change record holds 6 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

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

8 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 46d ago.

Building

  • Building activityMeasuredRead 15h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 2d ago.

Code and packages

  • Repository detailsMeasuredRead 6d ago.
  • Published packagesMeasuredRead 6d 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