> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/references/references-classic/glossary-classic/package-classic.md).

# Package (classic)

A package is an object that represents a software product in its distributable form. Packages can be installed on a device or uninstalled from a device.

Nexthink classifies packages into two types:

**Program**\
A program package holds a complete software product ready for installation.

**Update**\
An update package, also called a patch, holds bug fixes, security fixes and any other kind of improvements for a program package.

Packages should not be confused with applications. Packages represent a software product in its installable form. Applications represent a software product in its executable form. The Nexthink solution detects the presence of a package when it is installed, and acknowledges the presence of an application when it is executed.

The link between an application and a corresponding package cannot always be established, so you cannot navigate from one to the other. Sometimes, the link is known for individual executables of an application. If this is the case, you can find the name of the package in the field **packages** of the executable. One executable can in fact be linked to several packages, yet only the names of the packages are given and drilling down from executables to packages is not allowed either.

***

RELATED TOPICS

* [Binary](/platform/references/references-classic/glossary-classic/binary-classic.md)
* [Executable](/platform/references/references-classic/glossary-classic/executable-classic.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nexthink.com/platform/references/references-classic/glossary-classic/package-classic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
