folio 0.3.0
Tiny static javascript build and serve utility.
folio@0.3.0 was published on 2012-07-01. Its manifest declares 5 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= v0.4.8.
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
All folio versions · Permanent reference to 0.3.0 · Latest release
Package specifications
| Version | 0.3.0 |
|---|---|
| License declaration | Not declared |
| Published | 2012-07-01T02:47:15.605Z |
| Node.js requirement | >= v0.4.8 |
| Type declarations | Not declared |
| Runtime dependency count | 5 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | Not supplied |
| Published file count | Not supplied |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | index |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 8 |
| Repository stars | 843 |
| Repository forks | 27 |
Install folio 0.3.0
npm install folio@0.3.0 pnpm add folio@0.3.0 yarn add folio@0.3.0
Runtime dependencies
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- breeze@0.3.0 — direct
- drip@0.3.1 — direct
- filtr@0.3.0 — indirect
- fsagent@0.2.1 — direct
- oath@0.2.3 — indirect
- quantum@0.3.1 — direct
- sherlock@0.1.1 — indirect
- uglify-js@1.3.5 — direct
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
OpenSSF repository checks
Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.
| Maintained | 0/10 — project is archived |
|---|---|
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
| Security-Policy | 10/10 — security policy file detected |
| Code-Review | 2/10 — Found 7/30 approved changesets -- score normalized to 2 |
| Token-Permissions | 0/10 — detected GitHub workflow tokens with excessive permissions |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| Pinned-Dependencies | 0/10 — dependency not pinned by hash detected -- score normalized to 0 |
| CII-Best-Practices | 0/10 — no effort to earn an OpenSSF best practices badge detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/folio/0.3.0 — retrieved 2026-10-29T11:37:44.302Z
- https://api.deps.dev/v3/projects/github.com%2FMicrosoft%2Ffolio — retrieved 2026-10-29T10:24:01.026Z
- https://api.deps.dev/v3/systems/npm/packages/folio/versions/0.3.0 — retrieved 2026-10-29T11:37:44.949Z
- https://api.deps.dev/v3/systems/npm/packages/folio/versions/0.3.0:dependencies — retrieved 2026-10-29T11:37:44.981Z