npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@objectstack/service-settings

v6.9.0

Published

Settings service for ObjectStack — manifest registry + K/V resolver (Env > Tenant > User > Default) + REST routes. See ADR-0007.

Downloads

2,710

Readme

@objectstack/service-settings

Settings service for ObjectStack. Implements ADR-0007: a generic namespace manifest mechanism + a single K/V table (sys_setting) + a resolver that layers Env > Tenant > User > Default.

What it gives you

  • SettingsServicePlugin — registers the sys_setting schema, exposes a settings service in the kernel, and mounts REST routes on the HTTP server (when one is available).
  • SettingsService (kernel.getService('settings'))
    • get(ns, key, ctx) / getNamespace(ns, ctx) — resolved values with { value, source, locked }.
    • set(ns, key, value, scope, ctx) / setMany(...) — writes that persist into sys_setting. Throws when the effective value is locked by env.
    • registerManifest(manifest) / listManifests() / getManifest(ns).
    • runAction(ns, actionId, input, ctx) — for "test connection", "rotate", etc. declared in action_button specifiers.
  • REST routes (default base path /api/settings):
    • GET /api/settings → manifests visible to caller
    • GET /api/settings/:namespace{ manifest, values }
    • PUT /api/settings/:namespace → batch upsert
    • POST /api/settings/:namespace/:actionId → invoke declared action

Env override

process.env[NAMESPACE_KEY] (uppercased) takes precedence over any stored value. Such fields are returned with source: 'env', locked: true and writes (service or REST) fail with HTTP 409.

Encryption

Specifier.encrypted: true (implicit for password) round-trips the value through a pluggable CryptoAdapter. The default NoopCryptoAdapter is a base64 wrapper — production deployments must provide a real KMS adapter via plugin options.

Audit

Every write emits a sys_audit_log row (when the audit service is present). Encrypted values are masked with '<encrypted>' + checksum.

Always-on default

SettingsServicePlugin is part of the default capability slate — it is auto-mounted by objectstack serve (any preset except --preset minimal) and by mountDefaultProjectPlugins() on every per-project kernel on hosted objectos. Apps no longer need to declare requires: ['settings']. Apps with zero registered manifests pay no runtime cost (the registry is empty, no routes fire).

The Settings hub in apps/console therefore appears in every app, and the following built-in manifests are pre-registered out of the box:

| Namespace | Owner plugin | Highlights | |----------------|-----------------------------|---------------------------------------------| | mail | EmailServicePlugin | SMTP / Resend / Postmark + mail/test | | storage | StorageServicePlugin | Local FS / S3 + encrypted secret + storage/test | | branding | (built-in fallback) | Workspace name, logo, accent colour | | feature_flags| (built-in fallback) | Opt-in experimental features |

License

Apache-2.0. See LICENSING.md.