# shell-trigger

> Fires a callback, or kills process entirely, when a user accesses the server's shell

Latest version **0.1.2** (published 2013-05-25) · 0 weekly downloads

## Install

```sh
npm install shell-trigger
pnpm add shell-trigger
yarn add shell-trigger
bun add shell-trigger
```

## Health

**Score 10/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; low quality score; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.1.2 |
| Published | 2013-05-25 |
| First published | 2013-05-22 |
| Weekly downloads | 0 |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| Author | Philip Orange |
| Maintainers | philiporange |

## Links

- npm: https://www.npmjs.com/package/shell-trigger
- Repository: https://github.com/philiporange/node-shell-trigger
- Issues: https://github.com/philiporange/node-shell-trigger/issues
- npm.io page: https://npm.io/package/shell-trigger

## Recent versions

- 0.1.2 (latest) — 2013-05-25
- 0.1.1 — 2013-05-22
- 0.1.0 — 2013-05-22

## README

## Shell Trigger

### About

It could happen to anyone. You've logged into shell on your production node.js server. You've executed Unix's `last` command—to see when you last logged in. Now you're having one of those heart-in-mouth moments as you see someone—apparently, but definitely not, you—logged in at 2am this morning. You were asleep then.

*Shell Trigger* executes a callback, and can kill the node process entirely, when a change is detected in the users list.


### Install

    npm install shell-trigger


### Usage

    options = {cb: -> console.log 'intrusion detected'}
    trigger = require('shell-trigger')(options)

---
_Source: https://npm.io/package/shell-trigger · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._