npm · npm:fscreen
fscreen active
Vendor agnostic access to the fullscreen spec api
The latest stable version of fscreen is 1.2.0, published on 2021-02-11. Verified by Vigia on 2026-11-12.
| Latest stable version | 1.2.0 |
|---|---|
| Published | 2021-02-11 21:18:24 UTC |
| Install | npm install fscreen@latest |
| Requires (engines) | none declared |
| Peer dependencies | — |
| Dist-tags | latest: 1.2.0 |
| License | MIT |
| Advisories on latest version | none known |
| Last verified | 2026-11-12 13:38:31 UTC |
| Sources | api.deps.dev, registry.npmjs.org, registry.npmjs.org |
Maintenance
| Activity | dormant |
|---|---|
| Last stable release | 2021-02-11 21:18:24 UTC · 2099 days ago |
| Stable releases in the last 12 months | 0 |
| Published versions | 5 |
Heuristic based only on release dates; it does not measure issue or security response times.
Version history
| Version | Published |
|---|---|
1.2.0 | 2021-02-11 21:18:24 UTC |
1.1.0 | 2020-09-11 22:00:17 UTC |
1.0.2 | 2017-08-14 23:44:44 UTC |
1.0.1 | 2017-06-04 20:46:03 UTC |
1.0.0 | 2017-04-29 18:18:49 UTC |
Showing the 5 most recent of 5 versions. JSON
Give your AI agent these facts
Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.
claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp
Add to CursorAdd to VS Code★ Star on GitHub
Any other MCP client
{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests
Frequently asked questions
What is the latest version of fscreen?
The latest stable version of fscreen is 1.2.0, published on 2021-02-11. Verified by Vigia on 2026-11-12.
How do I install the latest version of fscreen?
Run npm install fscreen@latest. The latest stable version is 1.2.0 (verified 2026-11-12).
Is fscreen deprecated?
No. fscreen is not marked as deprecated in the registry.
Which Node.js version does fscreen require?
fscreen 1.2.0 does not declare a Node.js version requirement.
Does fscreen 1.2.0 have known vulnerabilities?
No known advisories affect fscreen 1.2.0 according to the data Vigia checks.
Is fscreen still maintained?
fscreen published 0 stable releases in the last 12 months; the most recent was 2099 days ago. Activity: dormant.
Observed changes
No changes observed yet since Vigia started tracking this package.
Related packages
- update-diff
- ses
- request-compose
- asar
- @flmngr/flmngr-vue
- @braidai/lang
- @chakra-ui/react-use-previous
- react-slider
- rgb-hex
- run-jxa
- @prisma/internals
- tailwindcss-radix
Badges for your README
Show the latest version, maintenance status and deprecation status of this package. Copy the Markdown:
[](https://vigia.coredls.cloud/npm/fscreen) [](https://vigia.coredls.cloud/npm/fscreen) [](https://vigia.coredls.cloud/npm/fscreen)
For agents
GET https://vigia.coredls.cloud/v1/packages/npm/fscreen
GET https://vigia.coredls.cloud/v1/packages/npm/fscreen/versions/{version}