Archive integrity, expected files and versioned filename
Verification without theatre.
“Verified” means the named release checks were completed. It does not mean vulnerability-free, certified, or suitable for every environment.
Pattern scan for embedded credentials before release
Marketplace lint, TypeScript and production build
Anonymous and authenticated delivery boundaries
Documented runtime and dependency expectations
Claims, limitations and delivery scope reviewed before listing
What we publish
- Version, compatibility and required permissions
- Checks actually completed for the release
- Known limitations and adopter responsibilities
- License, update and support boundaries
What we never imply
- Formal compliance certification unless an identified accredited party performed it
- Guaranteed security or production suitability
- Customer results that have not been measured
- Automated payment or entitlement capabilities before they are live
Report a security concern privately to security@nurpam.in. Do not include live credentials in the first message.
Review components ↗