npm Status Component Snapshot
Pricing
from $43.00 / 1,000 apify actor run or buyer defined paid events
npm Status component names + operational status. Does not fetch your Actor run logs. $0.01 / component.
Pricing
from $43.00 / 1,000 apify actor run or buyer defined paid events
Rating
0.0
(0)
Developer
Zentra
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Existing-input compatibility alias for a redacted incident summary. It is never queried externally or returned verbatim.
Optional saved-task purpose label. It does not change the investigation scope or trigger a live run lookup.
Sample produces the deterministic Store-default report. Buyer-supplied classifies only redacted material entered here. Legacy startUrls is accepted as buyer-supplied but is never fetched.
Sample records are non-chargeable. Buyer-ready records charge only when redacted incident material is supplied.
Public source URL for Try.
[ { "url": "https://status.npmjs.org/api/v2/summary.json" }]Optional redacted reference label. It is acknowledged but never returned or resolved by this Actor.
Choose the stage the buyer reports. This is an intake classification, not a completed diagnosis.
Describe the buyer-reported symptom without credentials, personal data, raw customer records, or complete logs. Raw text is not returned in the dataset.
Optional high-level description of the submitted input. Do not include tokens, cookies, or personal data. Raw text is not returned.
Optional short error summary. Remove secrets and customer data; the Actor returns only signal labels, never this raw text.
Existing saved-task compatibility field. Labels are never resolved as Actors, URLs, datasets, or sources.
[]Incident-stage is the standard labelled order. Relevance remains available for existing saved tasks; one report is emitted per submitted incident.
Include the statement that supplied reference fields were not fetched or returned.
Include stage and keyword-derived labels without echoing buyer-supplied text.
Include a reminder that a change conclusion needs two buyer-supplied reports; no history is fetched or retained.