---
# System prepended metadata

title: npm Public Feedback Triage

---

# npm Public Feedback Triage

### Attendees

- Myles Borins (@mylesborins)
- Darcy Clarke (@darcyclarke)
- Edward Thomson (@ethompson)
- Meirav Feiler
- Scott Densmore
- Bryan Clark
- Ruy Adorno

### Agenda

### Package meta data

* [npm score](https://github.com/npm/feedback/discussions/66)
* [Add TypeScript type information to an npm package's page, and ideally in the search index](https://github.com/npm/feedback/discussions/64)
* [Show package usage by version](https://github.com/npm/feedback/discussions/60)
* [Show Bundlephobia or similar browser size stats on package pages](https://github.com/npm/feedback/discussions/65)
* [Make the repo for a package more prominent](https://github.com/npm/feedback/discussions/50)
* [Make it easier to identify the format of a package](https://github.com/npm/feedback/discussions/13)
* [Make it easier to identify system access required by a package (and changes to that access over time)](https://github.com/npm/feedback/discussions/14)

---

### Notes

#### npm scores

- Popularity / Quality / Mainenance data is only shown on search. We could include on a package landing page
- We should invest in making these existing metrics higher quality
- We might want to improve discoverability of being able to search by these metrics

#### TypeScript type information

- Would this information be part of the packument in the registry?
- There are other runtimes / languages. Should we privledge it? Many moons ago we could have done this for coffee script.
- Would this be something on publish via metadata or something that would be done via static analysis

#### Show package usage by version

- This would be dependent on how we do analytics
- Registry would have to do some work on how data is currently being stored, there would be some work to be done.

#### Show size stats

- Perhaps not something we should focus on initially
- Bundle size is higher effort lower reward compared to some of the other package information improvements we are talking about
- We can use bundle size to improve our metrics to some capacity
- We can link to bundlephobia and explain why we chose not to directly surface this information if we make a landing page explaining our scoring ideology

#### Make it easier to identify the format of a package

- We should perhaps start with one and add more identification over time
- Runtime vs syntax
- Identifying ESM