access-controls 0.3.12
rule based access-controls engine for node.js (browser compatible)
access-controls@0.3.12 was published on 2014-08-13. Its manifest declares 3 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.
All access-controls versions · Permanent reference to 0.3.12 · Latest release
Package specifications
| Version | 0.3.12 |
|---|---|
| License declaration | Public Domain |
| Published | 2014-08-13T13:04:04.118Z |
| Node.js requirement | Not declared |
| Type declarations | Not declared |
| Runtime dependency count | 3 |
| 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 | 5 |
| Repository stars | 6 |
| Repository forks | 7 |
Install access-controls 0.3.12
npm install access-controls@0.3.12 pnpm add access-controls@0.3.12 yarn add access-controls@0.3.12
Runtime dependencies
- lodash 2.4.1
- object-tree 0.2.5
- patrun 0.2.0
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.
- gex@0.1.4 — indirect
- lodash@2.4.1 — direct
- object-tree@0.2.5 — direct
- patrun@0.2.0 — direct
- 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 2/24 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 |
| License | 10/10 — license file detected |
| Fuzzing | 0/10 — project is not fuzzed |
| SAST | 0/10 — SAST tool is not run on all commits -- score normalized to 0 |
| Branch-Protection | 0/10 — branch protection not enabled on development/release branches |
Evidence and freshness
- https://registry.npmjs.org/access-controls/0.3.12 — retrieved 2026-10-29T23:51:56.752Z
- https://api.deps.dev/v3/projects/github.com%2Fnherment%2Fnode-access-controls — retrieved 2026-10-29T22:48:19.126Z
- https://api.deps.dev/v3/systems/npm/packages/access-controls/versions/0.3.12 — retrieved 2026-10-29T23:51:57.318Z
- https://api.deps.dev/v3/systems/npm/packages/access-controls/versions/0.3.12:dependencies — retrieved 2026-10-29T23:51:57.341Z