applause 1.0.2
Pattern replacer that helps create a human-friendly replaces.
applause@1.0.2 was published on 2015-08-20. Its manifest declares 3 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >= 0.10.0.
All applause versions · Permanent reference to 1.0.2 · Latest release
Package specifications
| Version | 1.0.2 |
|---|---|
| License declaration | MIT |
| Published | 2015-08-20T01:52:11.619Z |
| Node.js requirement | >= 0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| Peer requirement count | 1 |
| 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 | src/applause.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 7 |
| Repository stars | 29 |
| Repository forks | 22 |
Install applause 1.0.2
npm install applause@1.0.2 pnpm add applause@1.0.2 yarn add applause@1.0.2
Runtime dependencies
- cson-parser ^1.1.0
- js-yaml ^3.3.0
- lodash ^3.10.0
Peer requirements
- grunt >=0.4.0
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- argparse@1.0.10 — indirect
- coffee-script@1.12.7 — indirect
- cson-parser@1.3.5 — direct
- esprima@4.0.1 — indirect
- js-yaml@3.15.2 — direct
- lodash@3.10.1 — direct
- sprintf-js@1.0.3 — indirect
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.
| Dangerous-Workflow | 10/10 — no dangerous workflow patterns detected |
|---|---|
| Maintained | 0/10 — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0 |
| Code-Review | 0/10 — Found 2/28 approved changesets -- score normalized to 0 |
| 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 |
| Security-Policy | 0/10 — security policy file not detected |
| Fuzzing | 0/10 — project is not fuzzed |
| License | 10/10 — license file detected |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
Evidence and freshness
- https://registry.npmjs.org/applause/1.0.2 — retrieved 2026-10-29T16:08:27.912Z
- https://api.deps.dev/v3/projects/github.com%2FoutaTiME%2Fapplause — retrieved 2026-10-29T15:23:58.732Z
- https://api.deps.dev/v3/systems/npm/packages/applause/versions/1.0.2:dependencies — retrieved 2026-10-29T16:08:28.435Z
- https://api.deps.dev/v3/systems/npm/packages/applause/versions/1.0.2 — retrieved 2026-10-29T16:08:28.486Z