# securify

> run a browserify-like bundle inside a node-vm

Latest version **1.1.10** (published 2013-07-11) · MIT license · 0 weekly downloads

## Install

```sh
npm install securify
pnpm add securify
yarn add securify
bun add securify
```

## Health

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

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 1.1.10 |
| Published | 2013-07-11 |
| First published | 2013-05-17 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 7 |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 2 |
| Author | Dominic Tarr |
| Maintainers | dominictarr |

## Links

- npm: https://www.npmjs.com/package/securify
- Repository: https://github.com/dominictarr/securify
- Issues: https://github.com/dominictarr/securify/issues
- npm.io page: https://npm.io/package/securify

## Dependencies (7)

- [brfs](https://npm.io/package/brfs.md) 0.0.5
- [through](https://npm.io/package/through.md) ~2.3.4
- [optimist](https://npm.io/package/optimist.md) ~0.4.0
- [module-deps](https://npm.io/package/module-deps.md) >=0.10 <1
- [browser-pack](https://npm.io/package/browser-pack.md) ~0.9.1
- [bundle-metadata](https://npm.io/package/bundle-metadata.md) ~1.0.0
- [insert-module-globals](https://npm.io/package/insert-module-globals.md) 1.2

## Recent versions

- 1.1.10 (latest) — 2013-07-11
- 1.1.9 — 2013-06-23
- 1.1.8 — 2013-06-19
- 1.1.7 — 2013-06-04
- 1.1.6 — 2013-06-04
- 1.1.5 — 2013-06-04
- 1.1.4 — 2013-06-04
- 1.1.3 — 2013-06-03
- 1.1.2 — 2013-05-30
- 1.1.1 — 2013-05-21
- 1.1.0 — 2013-05-21
- 1.0.0 — 2013-05-17

## README

# securify


so, have a server,
and send it database customizations with http post.

replicate the snapshots between all instances.
(but for now, just a single instance)

Each instance gets a shoe server,
and can handle it's own pipes.
when a connection comes in,
it's routed to the correct db on it's path...

if there are multiple dbs, then route to the server that connection lives on.

every instance is a loadbalancer.

## self-similar?

hmm, so if I have a section that has http...
then I could just use that for the server.

just stick files directly into levelup.

POST /taco/myid < bundle.json

(which also gets replicated...)

you could also use a static http thing to host your static pages
directly from the database...

we'd just need a load balancer, and subdomain proxies.

## updating

when a db is updated, take it down, destroy all connections
then start it again.




``` js
function () {
  return foo;

}
```

## License

MIT

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