success-symbol 0.1.0
Cross-platform success symbol.
success-symbol@0.1.0 was published on 2015-05-28. Its manifest declares 0 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=0.10.0.
All success-symbol versions · Permanent reference to 0.1.0 · Latest release
Package specifications
| Version | 0.1.0 |
|---|---|
| License declaration | MIT |
| Published | 2015-05-28T03:38:44.445Z |
| Node.js requirement | >=0.10.0 |
| Type declarations | Not declared |
| Runtime dependency count | 0 |
| 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.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 0 |
| Repository stars | 4 |
| Repository forks | 0 |
Install success-symbol 0.1.0
npm install success-symbol@0.1.0 pnpm add success-symbol@0.1.0 yarn add success-symbol@0.1.0
Runtime dependencies
- None declared
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.
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.
| Binary-Artifacts | 10/10 — no binaries found in the repo |
|---|---|
| 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 0/1 approved changesets -- score normalized to 0 |
| SAST | 0/10 — no SAST tool detected |
| 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 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
| Security-Policy | 0/10 — security policy file not detected |
Evidence and freshness
- https://registry.npmjs.org/success-symbol/0.1.0 — retrieved 2026-10-29T09:39:15.515Z
- https://api.deps.dev/v3/systems/npm/packages/success-symbol/versions/0.1.0 — retrieved 2026-10-29T09:39:16.051Z
- https://api.deps.dev/v3/systems/npm/packages/success-symbol/versions/0.1.0:dependencies — retrieved 2026-10-29T09:39:16.076Z
- https://api.deps.dev/v3/projects/github.com%2Fjonschlinkert%2Fsuccess-symbol — retrieved 2026-10-29T09:39:16.661Z