Verify that a resource is official
Start from astro.build or Astro’s official documentation rather than relying on a similar-looking domain, advertisement, or copied installation guide. The approved project sources identify withastro/astro as the maintained framework repository and withastro/astro.build as the official website repository.
Before following instructions, compare these details:
| Resource | Verification signal | Useful check |
|---|---|---|
| Website | Uses the astro.build domain |
Inspect the complete address before entering information |
| Documentation | Is linked from Astro’s official site | Prefer current documentation over an undated tutorial |
| Framework source | Repository is under github.com/withastro/astro |
Read the repository name, owner, README, and license |
| Website source | Repository is under github.com/withastro/astro.build |
Do not confuse it with the framework repository |
| Community | Reached through current official material | Recheck links before joining or authorizing another service |
A correct domain or repository name is useful evidence, but it is not a permanent safety guarantee. Accounts, links, releases, dependencies, and community spaces can change, so verify the context of each action.
Check packages and commands before installing
The maintained framework README recommends npm create astro@latest; it also documents npm install astro for manual installation. Copy installation commands from the current official README or documentation, particularly when a third-party article adds flags, scripts, or packages.
Use a short review routine:
- Confirm the package name is exactly
astrowhen installing the framework. - Check that integrations are documented by Astro or linked from maintained project material.
- Review what a command will create or modify before running it.
- Treat requests for credentials, access tokens, wallet details, or unrelated software as reasons to stop and verify.
- Evaluate additional UI frameworks and integrations individually; official support does not make every project configuration appropriate.
Participate with appropriate caution
Official material directs project participation and contributions to GitHub and support or feedback to Astro’s Discord community. Follow those destinations through current first-party pages, review permissions during sign-in, and avoid sharing secrets, private source code, or production credentials in public issues or chat.
For suspected impersonation or a questionable package, pause installation and compare the link against Astro’s official website, documentation, and maintained repository.
