Protecting the web-pack bundles
- Dominant language
- No language data
- Stars
- 346
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
**Background**
Building an enterprise grade application in JS library or Framework could become challenging if most of the app functionality are distributed in the front end or JavaScript. Though webpack plugins like Uglify or webpack obfuscator only provide basic minification/obfuscation and can be quickly reversed with automated tools.
**Current Solutions**
There are some tools available in the market to overcome this situation, they do a techniques like reordering, encoding, splitting, renaming, and logic concealing.
**Proposed**
Would be great if we have a security layer with Azure Front-Door or CDN which is capable of checking the token from B2C.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue discusses JavaScript/webpack bundles and proposes an Azure Front Door or CDN security layer that checks a B2C token. Start by clarifying the intended token-checking flow and acceptance criteria; no files, tests, or implementation entry points are identified, and done would require a defined, implementable protection approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript, webpack
- Domain
- authentication, cloud, security, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100