Package Name Guidelines" (npm Docs)¶
Package Name Guidelines" (npm Docs).
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Appellation
- In software package ecosystems, a package name within a registry is an appellation: the entity is the package, the opaque token is the registered name, the registrar is the package index that guarantees uniqueness within its namespace, and the portable handle is what every dependency declaration routes through.
This sourceDocuments how a package name within the registry is an authoritative, namespace-unique identifier (uniqueness enforced at publish time; scopes for disambiguation), through which dependents refer to a package by name rather than contents — the indirection that lets maintainers ship new versions without invalidating downstream references.
- In software package ecosystems, a package name within a registry is an appellation: the entity is the package, the opaque token is the registered name, the registrar is the package index that guarantees uniqueness within its namespace, and the portable handle is what every dependency declaration routes through.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. The single citation of this work carries no recorded support check.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:9aafbc23a8c4 · see in the full table