seneca-perm 0.1.10
Seneca permissions plugin
seneca-perm@0.1.10 was published on 2014-07-10. Its manifest declares 2 runtime dependencies and 1 peer requirement. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All seneca-perm versions · Permanent reference to 0.1.10 · Latest release
Package specifications
| Version | 0.1.10 |
|---|---|
| License declaration | MIT |
| Published | 2014-07-10T09:57:08.561Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 2 |
| 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 | perm.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | 6 |
| Repository stars | 8 |
| Repository forks | 12 |
Install seneca-perm 0.1.10
npm install seneca-perm@0.1.10 pnpm add seneca-perm@0.1.10 yarn add seneca-perm@0.1.10
Runtime dependencies
- lodash 2.4.1
- access-controls 0.3.x
Peer requirements
- seneca *
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- access-controls@0.3.12 — direct
- gex@0.1.4 — indirect
- lodash@2.4.1 — direct
- object-tree@0.2.5 — indirect
- patrun@0.2.0 — indirect
- underscore@1.6.0 — 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.
| 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 1/25 approved changesets -- score normalized to 0 |
| Binary-Artifacts | 10/10 — no binaries found in the repo |
| 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/seneca-perm/0.1.10 — retrieved 2026-10-29T23:15:31.440Z
- https://api.deps.dev/v3/projects/github.com%2Frjrodger%2Fseneca-perm — retrieved 2026-10-29T22:44:57.585Z
- https://api.deps.dev/v3/systems/npm/packages/seneca-perm/versions/0.1.10 — retrieved 2026-10-29T23:15:31.970Z
- https://api.deps.dev/v3/systems/npm/packages/seneca-perm/versions/0.1.10:dependencies — retrieved 2026-10-29T23:15:31.998Z