Download the PHP package pushinbr/pam-native-plugin-kit without Composer
On this page you can find all versions of the php package pushinbr/pam-native-plugin-kit. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download pushinbr/pam-native-plugin-kit
More information about pushinbr/pam-native-plugin-kit
Files in pushinbr/pam-native-plugin-kit
Package pam-native-plugin-kit
Short Description Scaffold, validate and generate typed PAM Native plugins.
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-plugin-kit
Why PAM Native Plugin Kit
Scaffold, validate, and code-generate stable PAM Native plugins with protocol-safe enums, manifests, tests, and CI. 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 | Typed IDL · PHP/Kotlin/Swift code generation |
| Application model | Composer package + generated native integration |
| Design rule | Independent module; no feed, vertical, or application template bundled |
What you can build
- Wrapping an internal native SDK
- Publishing a focused community capability
- Generating parity-safe cross-platform bridge code
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
The official toolchain for building real PAM Native ecosystem packages. It validates plugin manifests, compiles one typed IDL into PHP, Kotlin and Swift, and scaffolds cross-platform packages with CI from the first commit.
Typed IDL
Coded variants are integer enums with sequential values beginning at 1.
The compiler rejects gaps and string variants so PHP, Kotlin and Swift cannot
silently disagree about wire values.
Generated sources are deterministic and suitable for committing or checking
in CI. The plugin manifest and IDL digests are recorded by PAM Native in
.pam-native/plugins.lock.json.
Portable contributor certification
conformance is a non-mutating, dependency-free package audit that can run
before native SDK jobs. It emits schema 1, Native surfaceCode: 2, sequential
integer result/check codes, and SHA-256 evidence for seven bounded checks:
- manifest validation;
- typed IDL compilation;
- byte-for-byte PHP/Kotlin/Swift generation determinism;
- Composer plugin metadata;
- declared Kotlin source evidence;
- declared Swift source evidence;
- the portable PHP test entrypoint.
The runner reads at most 1 MiB per document, 256 native source files and 16 MiB
per platform. Package paths are confined segment-by-segment; symlinks,
traversal, duplicate source evidence and empty native source sets fail closed.
The JSON contract is
resources/pam-native-conformance.schema.json. This portable report does not
replace Android/iOS compilation, device tests, signing or store validation.
What installation does
pam composer require pushinbr/pam-native-plugin-kit installs the package through the project's normal composer.json and composer.lock. Run pam doctor --fix afterward to validate the environment and regenerate native integration when required.
Use pam packages to inspect direct installed Composer dependencies and pam composer remove pushinbr/pam-native-plugin-kit to uninstall the capability.
API guide
| API | Responsibility |
|---|---|
Scaffolder |
Create a cross-platform plugin repository with CI. |
ManifestValidator |
Validate plugin metadata, native sources, and declared contracts. |
IdlCompiler |
Generate deterministic PHP, Kotlin, and Swift types from one IDL. |
Diagnostic / ValidationResult |
Consume typed validation findings in tooling or CI. |
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
- Commit generated sources and verify regeneration is clean in CI.
- Use sequential integer enums beginning at
1in every wire contract. - Pin native requirements and record manifest/IDL digests.
- 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
- Validation reports missing files: compare paths with the package root in the manifest.
- Generated languages disagree: remove handwritten copies and regenerate from the IDL.
- CI has a dirty diff: run compile locally and commit deterministic output.
- Native integration is stale: run
pam doctor --fix, rebuild the native host, and inspect the first reported diagnostic.
Compatibility and support
This package targets PHP 8.5 and 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.
