Suggestion: Weekly/Monthly/Yearly Hits

[ghost]

Hey, @cdnjs team. I have a suggesting regarding hits. We can have a item in the api response json regarding hits. JsDelivr also provides an api and It is widely used for badges like . Likewise If cdnjs.com also has a similar api it would be really useful

[MattIPv4]

👋 The short answer is that we don't have this data available in the API currently as we avoid doing tracking wherever possible.

@xtuc thoughts on if we can get this data made available in the API?

[ghost]

@MattIPv4 Hits = No. Of Requests Made. And This Data Would Be There Already I Think?

[MattIPv4]

We do not have access to hit data in the API, we do not actively track requests through any cdnjs operations.

The only place that this data will exist currently is within Cloudflare's standard logging system.

[ghost]

I don't know much about cloudflare. But the example I gave also uses cloudflare and many more alike. But still provides the count. I think that cdnjs only uses cloudflare so it might be easy to integrate. I've used jsdelivr before as well when the package I wanted was not there on cdnjs. And it doesn't send any cookies or something else for getting the data. I think that jsdelivr's repo can be a example of implentation of this without the need of tracking or something

[MattIPv4]

I think you misunderstand what I mean by tracking here -- we do not actively track any metrics on requests that are made to cdnjs in a way that makes data available to us for an API endpoint, including request count.

By the domain going through Cloudflare, they have basic request information logged and we could potentially use that to power an API endpoint to get hits for a library over a time period, but we do not currently have access to that data other than through manual requests that we make once a month for cdnjs/cf-stats.

I defer to @xtuc on if they think it'd be viable to get real-time access to Cloudflare data for an API endpoint, or if it'd be worth the investment to add our own request logging as middleware in a Worker, or if we should just continue to not offer an API endpoint for hits?

[ghost]

@xtuc??

[Explosion-Scratch]

I would only be comfortable if all the data was anonymous, and then somehow opt-outable? (Not sure how that would work but it's something to consider)

[MattIPv4]

All the data we publish will always be anonymized and aggregated :)

I'm not sure how opt-out would function in this context?

[Explosion-Scratch]

All the data we publish will always be anonymized and aggregated :)

I'm not sure how opt-out would function in this context?

Possibly noreferrer or something in script tags could be taken as indication the script doesn't count? This could be done server side as well.

[MattIPv4]

We already set noreferrer on all cdnjs script/link tags -- we don't track anything like that, we just track a total request count for each asset