HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
IBM
import-tracker
Python2022–2022
IBM / import-tracker

import-tracker

Python utility for tracking third party dependencies within a library

Libraries & SDKs
Explore on GitHubRead Hacker News discussions
2Distinct people
3Mentions
0Explicit recommenders
461GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Python utility for tracking third party dependencies within a library

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, 1:49:46 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 hour3 dated mentions

Observed mentions: 2022-05-25 03:34:58 UTC to 2022-05-25 20:22:37 UTC.

012022-05-25 03:00:00 UTC to 2022-05-25 04:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 25, 03:002022-05-25 04:00:00 UTC to 2022-05-25 05:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 05:00:00 UTC to 2022-05-25 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 06:00:00 UTC to 2022-05-25 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 07:00:00 UTC to 2022-05-25 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 08:00:00 UTC to 2022-05-25 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 09:00:00 UTC to 2022-05-25 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 10:00:00 UTC to 2022-05-25 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 11:00:00 UTC to 2022-05-25 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 25, 11:002022-05-25 12:00:00 UTC to 2022-05-25 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 13:00:00 UTC to 2022-05-25 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 14:00:00 UTC to 2022-05-25 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 15:00:00 UTC to 2022-05-25 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 16:00:00 UTC to 2022-05-25 17:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2022-05-25 17:00:00 UTC to 2022-05-25 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 18:00:00 UTC to 2022-05-25 19:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 19:00:00 UTC to 2022-05-25 20:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-05-25 20:00:00 UTC to 2022-05-25 21:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMay 25, 20: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
May 25, 03:002022-05-25 03:00:00 UTC2022-05-25 04:00:00 UTC110
May 25, 04:002022-05-25 04:00:00 UTC2022-05-25 05:00:00 UTC000
May 25, 05:002022-05-25 05:00:00 UTC2022-05-25 06:00:00 UTC000
May 25, 06:002022-05-25 06:00:00 UTC2022-05-25 07:00:00 UTC000
May 25, 07:002022-05-25 07:00:00 UTC2022-05-25 08:00:00 UTC000
May 25, 08:002022-05-25 08:00:00 UTC2022-05-25 09:00:00 UTC000
May 25, 09:002022-05-25 09:00:00 UTC2022-05-25 10:00:00 UTC000
May 25, 10:002022-05-25 10:00:00 UTC2022-05-25 11:00:00 UTC000
May 25, 11:002022-05-25 11:00:00 UTC2022-05-25 12:00:00 UTC000
May 25, 12:002022-05-25 12:00:00 UTC2022-05-25 13:00:00 UTC000
May 25, 13:002022-05-25 13:00:00 UTC2022-05-25 14:00:00 UTC000
May 25, 14:002022-05-25 14:00:00 UTC2022-05-25 15:00:00 UTC000
May 25, 15:002022-05-25 15:00:00 UTC2022-05-25 16:00:00 UTC000
May 25, 16:002022-05-25 16:00:00 UTC2022-05-25 17:00:00 UTC110
May 25, 17:002022-05-25 17:00:00 UTC2022-05-25 18:00:00 UTC000
May 25, 18:002022-05-25 18:00:00 UTC2022-05-25 19:00:00 UTC000
May 25, 19:002022-05-25 19:00:00 UTC2022-05-25 20:00:00 UTC000
May 25, 20:002022-05-25 20:00:00 UTC2022-05-25 21:00:00 UTC101

What Hacker News says

3 sources
cubes·May 25, 2022
This looks really neat. One thing I noticed on reading the source code, it appears to actually import the modules: Quoting the docstring on the `track_module` function: """This function executes the tracking of a single module by launching a subprocess to execute this module against the target module. The implementation of thie tracking resides in the __main__ in order to carefully control the import ecosystem. Source: https://github.com/IBM/import-tracker/blob/67a1e84e5a609e52e... Here's the actual subprocess call: https://github.com/IBM/import-tracker/blob/67a1e84e5a609e52e... # Launch the process proc = subprocess.Popen(shlex.split(cmd), stdout=subprocess.PIPE, env=env) I think this is clever, and maybe even necessary, but feels risky to do on unaudited third-party Python libraries. Maybe I'm misunderstanding
Read the rest
something?
In Python utility for tracking third party dependencies within a library

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.