
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Zero-trust security for every web app. Protect MVC web apps and RESTful APIs with a multi-stage security pipeline that includes XSS detection, authentication, IP firewall, two-factor, activity/data authorization, account verification and suspension checks. Available for all major platforms including .NET Framework MVC/Web API, .NET Core and Service Stack. To get started Visit https://ASPSecurityKit.net/docs/getting-started/ This is the base platform-agnostic package. To get started You should also install one of the platform specific packages such as ASPSecurityKit.NetCore, ASPSecurityKit.NetFramework.Mvc, ASPSecurityKit.NetFramework.WebApi or ASPSecurityKit.ServiceStack. Additionally, ASPSecurityKit also provides drop-in source code packages for both API and MVC web apps giving you end-to-end implementation of commonly needed functionality including login, register, forgot password, account settings (change email/password), user management, permission management, administration (impersonation), localization, production-grade graceful error handling etc. To download these source code packages into your project, install ASPSecurityKit.Tools package if you haven't already and execute start-ask command in Visual Studio Package Manager Console. For more information, visit https://ASPSecurityKit.net/docs/source-packages/ Commonly Used Types: ASPSecurityKit.ISecurityPipeline ASPSecurityKit.IUserService
FAQs
Zero-trust security for every web app. Protect MVC web apps and RESTful APIs with a multi-stage security pipeline that includes XSS detection, authentication, IP firewall, two-factor, activity/data authorization, account verification and suspension checks. Available for all major platforms including .NET Framework MVC/Web API, .NET Core and Service Stack. To get started Visit https://ASPSecurityKit.net/docs/getting-started/ This is the base platform-agnostic package. To get started You should also install one of the platform specific packages such as ASPSecurityKit.NetCore, ASPSecurityKit.NetFramework.Mvc, ASPSecurityKit.NetFramework.WebApi or ASPSecurityKit.ServiceStack. Additionally, ASPSecurityKit also provides drop-in source code packages for both API and MVC web apps giving you end-to-end implementation of commonly needed functionality including login, register, forgot password, account settings (change email/password), user management, permission management, administration (impersonation), localization, production-grade graceful error handling etc. To download these source code packages into your project, install ASPSecurityKit.Tools package if you haven't already and execute start-ask command in Visual Studio Package Manager Console. For more information, visit https://ASPSecurityKit.net/docs/source-packages/ Commonly Used Types: ASPSecurityKit.ISecurityPipeline ASPSecurityKit.IUserService
We found that aspsecuritykit demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.