Download the PHP package pushinbr/pam-native-feature-flags without Composer
On this page you can find all versions of the php package pushinbr/pam-native-feature-flags. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pushinbr/pam-native-feature-flags
More information about pushinbr/pam-native-feature-flags
Files in pushinbr/pam-native-feature-flags
Package pam-native-feature-flags
Short Description Typed targeting, deterministic rollouts and offline feature-flag snapshots for PAM Native.
License Apache-2.0
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package pam-native-feature-flags
Why PAM Native Feature Flags
Evaluate flags locally from signed or cached snapshots, keep variants integer-backed, and make rollout behavior testable offline. The public API is strictly typed for PHP 8.5; expensive or frame-sensitive work stays in Rust or the platform SDK instead of crossing the application boundary every frame.
| Best for | A focused capability you can add to any PAM Native application |
| Native path | Deterministic local evaluator |
| Application model | Composer package + generated native integration |
| Design rule | Independent module; no feed, vertical, or application template bundled |
What you can build
- Percentage and cohort rollouts
- Kill switches for risky native capabilities
- Offline experiments with deterministic assignment
Quick start
Already have a PAM Native project? Add only this capability:
New to PAM? Follow the five-minute PAM Native setup once, then return here. Your application stays a normal Composer project with a committed lockfile.
See it in action
Typed feature flags with deterministic targeting, percentage rollouts, local overrides, exposure events, integer kill switches and offline native snapshots. Production snapshots can be authenticated with Ed25519, bounded to one MiB, expired locally, and pinned to an explicit key-id allowlist before parsing.
Rollouts use SHA-256 over flag-key + NUL + bucketing-id, then map the first
unsigned 32 bits into 0...9999. Golden tests keep PHP, Kotlin and Swift
assignments identical. Snapshot payloads are bounded to one MiB.
What installation does
pam add feature-flags resolves the official compatible package, performs a non-mutating Composer preflight, updates the normal composer.json and composer.lock, refreshes generated native integration when required, and leaves the project ready for pam doctor validation.
Use pam packages to inspect availability and pam remove feature-flags to uninstall the capability safely. Direct Composer commands are an advanced interoperability path; PAM is the supported application workflow.
API guide
| API | Responsibility |
|---|---|
FeatureFlags |
Evaluate typed flags and manage local overrides. |
FlagDefinition / TargetingRule |
Declare defaults, rules, and rollouts. |
EvaluationContext |
Provide a stable bucketing identifier and attributes. |
SnapshotStore |
Persist bounded offline-native snapshots. |
SignedFlagSnapshot |
Verify revisioned, expiring Ed25519 configuration envelopes before activation. |
FlagProvider |
Supply definitions from memory, JSON, or a custom backend. |
All coded states, kinds, and variants are sequential integer-backed enums. Use enum cases in application code; do not depend on raw wire numbers.
Production checklist
- Use a stable, non-secret bucketing identifier across sessions.
- Emit exposure events once per product decision, not every render.
- Always provide a safe default for offline and malformed configurations.
- Sign remote snapshots, pin trusted public keys in the app, reject revision rollback, and activate only after verification.
- Run
pam doctor,pam test, and a signed release build on every supported platform. - Exercise denial, cancellation, backgrounding, process restart, and offline behavior before release.
Troubleshooting
- Users change buckets: verify the bucketing identifier is stable.
- A rule never matches: inspect attribute types as well as values.
- Snapshot save fails: keep the serialized payload below the documented one-MiB bound.
- Native integration is stale: run
pam doctor --fix, rebuild the native host, and inspect the first reported diagnostic.
Compatibility and support
This package targets PAM Native 0.8.x, Android API 26+, and iOS 15+ unless a platform-specific section above states a stricter requirement. Platform SDKs, credentials, entitlements, physical hardware, and store configuration remain application responsibilities.
Security vulnerabilities should be reported through the repository security policy or GitHub private vulnerability reporting, not a public issue.
