docs: promote Threat Intelligence npm features out of beta (#50)

Removes the "(Beta)" status designation from the Threat Intelligence API
NPM features docs so the feature reads as a live, supported capability:

- astro.config.mjs: sidebar label "NPM features (Beta)" -> "NPM features"
  and removed the "Beta" tip badge on the NPM features group.
- beta.md: title -> "NPM features"; reworded beta/pre-GA status prose to
  neutral language and removed the "spec may change without a version
  bump while in beta" caveat.
- overview.md: heading, link text and table label -> "NPM features";
  reworded status prose; removed the beta spec-stability caveat.
- threat-intel-beta.yaml: reworded info.description and related-page link,
  server display description "Beta" -> "NPM features", and info.version
  "beta" -> "1.0".

Deliberately unchanged: the /beta/ page URL and slug, the
api-reference/threat-intelligence-beta route, schema/collection filenames,
and the live API endpoint path /database/api/beta/.

Co-authored-by: Claude <noreply@anthropic.com>

Author: claude[bot]

astro.config.mjs

@@ -106,7 +106,7 @@ export default defineConfig({
 					{
 						base: 'api-reference/threat-intelligence-beta',
 						schema: './public/schemas/threat-intel-beta.yaml',
-						sidebar: { label: 'NPM features (Beta)', group: threatIntelBetaSidebarGroup, collapsed: true },
+						sidebar: { label: 'NPM features', group: threatIntelBetaSidebarGroup, collapsed: true },
 					},
 				]),
 			],
@@ -169,7 +169,6 @@ export default defineConfig({
 								threatIntelExtendedSidebarGroup,
 								{
 									label: 'NPM features',
-									badge: { text: 'Beta', variant: 'tip' },
 									collapsed: true,
 									items: [
 										{ slug: 'api-solutions/threat-intelligence-api/beta' },

public/schemas/threat-intel-beta.yaml

@@ -1,10 +1,10 @@
 openapi: 3.1.0
 info:
   title: Patchstack Threat Intelligence API — NPM features
-  version: beta
+  version: '1.0'
   summary: npm + WordPress vulnerability intelligence with nested response shape and cursor pagination.
   description: |
-    The Beta endpoints live alongside the v2 API and add npm coverage, an optional
+    The npm endpoints live alongside the v2 API and add npm coverage, an optional
     full advisory body, a consistent nested response shape, and cursor pagination.
     They are the recommended endpoints for new integrations; v2 remains available
     for backwards compatibility.
@@ -64,7 +64,7 @@ info:
 
     ## Related pages
 
-    - Narrative guide with code samples: [NPM features (Beta)](/api-solutions/threat-intelligence-api/beta/)
+    - Narrative guide with code samples: [NPM features](/api-solutions/threat-intelligence-api/beta/)
     - OpenAPI spec (import into Postman / Insomnia / Bruno / Hoppscotch): <https://docs.patchstack.com/schemas/threat-intel-beta.yaml>
     - Postman collection (pre-imported): <https://docs.patchstack.com/schemas/threat-intel-beta.postman_collection.json>
 
@@ -76,7 +76,7 @@ info:
 
 servers:
   - url: https://vdp-api.patchstack.com/database/api/beta
-    description: Beta
+    description: NPM features
 
 security:
   - PSKey: []

src/content/docs/API solutions/Threat Intelligence API/beta.md

@@ -1,5 +1,5 @@
 ---
-title: "NPM features (Beta)"
+title: "NPM features"
 excerpt: "npm-ecosystem coverage and the supporting additions on top of the Threat Intelligence API — the /all endpoint, cursor pagination, ?include=details, and the nested response shape."
 hidden: false
 metadata:
@@ -12,7 +12,7 @@ sidebar:
   label: "Overview"
 ---
 
-_The Beta surface extends the Threat Intelligence API ahead of GA. It runs at a separate base URL, ships its own OpenAPI spec, and is available to **selected partners working directly with Patchstack**. The shared endpoints (`/latest`, `/product/{type}/{name}/{version}`, `/product/{type}/{name}/{version}/exists`, `/batch`) behave the same as the stable API but accept extra parameters and return a nested response shape. This page documents only what's new — for the full spec including npm-flavour examples, see the [auto-generated reference](/api-reference/threat-intelligence-beta/). [Contact us](https://patchstack.com/for-hosts/) if you'd like access._
+_The npm features extend the Threat Intelligence API with npm-ecosystem coverage. They run at a separate base URL, ship their own OpenAPI spec, and are available to **selected partners working directly with Patchstack**. The shared endpoints (`/latest`, `/product/{type}/{name}/{version}`, `/product/{type}/{name}/{version}/exists`, `/batch`) behave the same as the stable API but accept extra parameters and return a nested response shape. This page documents only what's new — for the full spec including npm-flavour examples, see the [auto-generated reference](/api-reference/threat-intelligence-beta/). [Contact us](https://patchstack.com/for-hosts/) if you'd like access._
 
 ## Base URL
 
@@ -30,9 +30,7 @@ https://vdp-api.patchstack.com/database/api/beta/
 | `?include=details` | List endpoints — adds an `advisory_details` markdown field to each item (npm). |
 | Nested response shape | All list endpoints — `product`, `cvss`, `cwe`, `version_info` objects in place of the v2 flat shape. |
 
-The full Beta schema (every endpoint, parameter, response example) lives in the [auto-generated reference](/api-reference/threat-intelligence-beta/).
-
-> **Spec stability:** the Beta spec may change without a version bump while the API is in beta. Pin a commit of the YAML in production integrations, or wait for the GA release when versioned URLs ship.
+The full npm-features schema (every endpoint, parameter, response example) lives in the [auto-generated reference](/api-reference/threat-intelligence-beta/).
 
 ## Pagination
 
@@ -58,15 +56,15 @@ npm package slugs that include a `/` (e.g. `@scope/pkg`) conflict with the route
 
 ## Errors
 
-In addition to the [stable error codes](/api-solutions/threat-intelligence-api/extended/#errors), Beta returns:
+In addition to the [stable error codes](/api-solutions/threat-intelligence-api/extended/#errors), the npm endpoints return:
 
 | Status | Meaning |
 |---|---|
 | `422 Unprocessable Entity` | Invalid parameter combination (e.g. `cursor` + `page`), invalid `platform`, or `per_page > 500`. |
 
-## Migration notes (stable v2 → beta)
+## Migration notes (stable v2 → npm endpoints)
 
-- Beta npm responses use **nested objects** (`product`, `cvss`, `cwe`, `capec`, `version_info`) whereas the v2 shape is flat. Update parsers accordingly.
+- npm responses use **nested objects** (`product`, `cvss`, `cwe`, `capec`, `version_info`) whereas the v2 shape is flat. Update parsers accordingly.
 - `ghsa_id` was renamed to `ghsa` at the top level.
 - `direct_url` was renamed to `url` (the npm-flavoured shape exposes a single URL only).
 - The `description` field was dropped for npm (the title already includes it).

src/content/docs/API solutions/Threat Intelligence API/overview.md

@@ -18,11 +18,11 @@ Custom pricing, activated on request — [contact us](https://patchstack.com/for
 
 - [Guide](/api-solutions/threat-intelligence-api/extended/) · [Reference](/api-reference/threat-intelligence-extended/) · [OpenAPI](/schemas/threat-intel-extended.yaml) · [Postman](/schemas/threat-intel-extended.postman_collection.json) · [API properties](/api-solutions/threat-intelligence-api/api-properties/)
 
-## NPM features (Beta)
+## NPM features
 
-For partners covering JavaScript components, a Beta surface adds **npm-ecosystem coverage** alongside WordPress, available to **selected partners working directly with Patchstack**. Beyond npm itself it ships the supporting additions that make npm coverage workable at scale: the new `GET /all` endpoint, cursor pagination, `?include=details` for full advisory bodies, and a nested response shape the stable API will eventually adopt. Everything else (`/latest`, `/product/{type}/{name}/{version}`, `/batch`) is the same surface as the stable API.
+For partners covering JavaScript components, the npm features add **npm-ecosystem coverage** alongside WordPress, available to **selected partners working directly with Patchstack**. Beyond npm itself they ship the supporting additions that make npm coverage workable at scale: the new `GET /all` endpoint, cursor pagination, `?include=details` for full advisory bodies, and a nested response shape the stable API will eventually adopt. Everything else (`/latest`, `/product/{type}/{name}/{version}`, `/batch`) is the same surface as the stable API.
 
-See the [NPM features (Beta)](/api-solutions/threat-intelligence-api/beta/) page for the full delta — base URL, parameters, pagination, errors, and migration notes — and the [auto-generated reference](/api-reference/threat-intelligence-beta/) for the full schema. [Contact us](https://patchstack.com/for-hosts/) for access.
+See the [NPM features](/api-solutions/threat-intelligence-api/beta/) page for the full delta — base URL, parameters, pagination, errors, and migration notes — and the [auto-generated reference](/api-reference/threat-intelligence-beta/) for the full schema. [Contact us](https://patchstack.com/for-hosts/) for access.
 
 ---
 
@@ -32,12 +32,12 @@ The legacy [Standard tier](/api-solutions/threat-intelligence-api/standard/) is
 
 ## Using the API with your tools
 
-The API ships with an OpenAPI spec and a generated Postman collection. Beta has its own spec — pick whichever you're integrating against:
+The API ships with an OpenAPI spec and a generated Postman collection. The npm features have their own spec — pick whichever you're integrating against:
 
 | | OpenAPI spec | Postman collection |
 |---|---|---|
 | Threat Intelligence API | [`threat-intel-extended.yaml`](/schemas/threat-intel-extended.yaml) | [`threat-intel-extended.postman_collection.json`](/schemas/threat-intel-extended.postman_collection.json) |
-| NPM features (Beta) | [`threat-intel-beta.yaml`](/schemas/threat-intel-beta.yaml) | [`threat-intel-beta.postman_collection.json`](/schemas/threat-intel-beta.postman_collection.json) |
+| NPM features | [`threat-intel-beta.yaml`](/schemas/threat-intel-beta.yaml) | [`threat-intel-beta.postman_collection.json`](/schemas/threat-intel-beta.postman_collection.json) |
 | Standard *(legacy)* | [`threat-intel-standard.yaml`](/schemas/threat-intel-standard.yaml) | [`threat-intel-standard.postman_collection.json`](/schemas/threat-intel-standard.postman_collection.json) |
 
 ### Postman, Insomnia, Bruno or Hoppscotch
@@ -78,5 +78,3 @@ npx @openapitools/openapi-generator-cli generate \
 ```
 
 Speakeasy and Fern also consume the same spec and produce more idiomatic SDKs if you need a polished client library.
-
-> **Spec stability:** the Beta spec may change without a version bump while the API is in beta. Pin a commit of the YAML in production integrations, or wait for the GA release when we'll publish versioned URLs. The stable spec tracks the v2 surface.