HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
droundy
arrayref
Rust2026–2026
droundy / arrayref

arrayref

Two macros for taking array references in rust.

2Distinct people
2Mentions
0Explicit recommenders
91GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Two macros for taking array references in rust.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 7:56:55 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2026-08-20 09:25:51 UTC to 2026-08-20 15:00:10 UTC.

012026-08-20 09:00:00 UTC to 2026-08-20 10:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsAug 20, 09:002026-08-20 10:00:00 UTC to 2026-08-20 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-20 11:00:00 UTC to 2026-08-20 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-20 12:00:00 UTC to 2026-08-20 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 20, 12:002026-08-20 13:00:00 UTC to 2026-08-20 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-20 14:00:00 UTC to 2026-08-20 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-08-20 15:00:00 UTC to 2026-08-20 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 20, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 20, 09:002026-08-20 09:00:00 UTC2026-08-20 10:00:00 UTC110
Aug 20, 10:002026-08-20 10:00:00 UTC2026-08-20 11:00:00 UTC000
Aug 20, 11:002026-08-20 11:00:00 UTC2026-08-20 12:00:00 UTC000
Aug 20, 12:002026-08-20 12:00:00 UTC2026-08-20 13:00:00 UTC000
Aug 20, 13:002026-08-20 13:00:00 UTC2026-08-20 14:00:00 UTC000
Aug 20, 14:002026-08-20 14:00:00 UTC2026-08-20 15:00:00 UTC000
Aug 20, 15:002026-08-20 15:00:00 UTC2026-08-20 16:00:00 UTC101

What Hacker News says

1 sources
GitHub really needs something finer-grain then just pretending the repo never existed during these incidents. [1] The bad package version has also just disappeared from crates.io [2] with no indication its been yanked. There's no security advisory there either [3] "No advisories found for this crate." I feel crates.io was unprepared for a security incident like this since they're managing the response [4] [1]: https://web.archive.org/web/20260820145918/https://github.co... [2]: https://crates.io/crates/arrayref/versions [3]: https://crates.io/crates/arrayref/security (I'd give an Wayback link but that's also broken https://web.archive.org/web/20260820150747/https://crates.io...) [4]: https://github.com/rustsec/advisory-db/issues/3161#issuecomm...
In Malicious Rust crate Arrayref runs a build-time payload

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.