elhebert/laravel-sri
Composer 安装命令:
composer require elhebert/laravel-sri
包简介
Subresource Integrity hash generator for laravel
README 文档
README
Small Laravel 8+ package that'll generate the integrity hashes for your style and script files.
For Laravel 5.5+ support, use the v1 branch. For Laravel 6+ support, use the v2 branch.
About Subresources Integrity
From MDN:
Subresource Integrity (SRI) is a security feature that enables browsers to verify that files they fetch (for example, from a CDN) are delivered without unexpected manipulation. It works by allowing you to provide a cryptographic hash that a fetched file must match.
Troy Hunt wrote an article speaking on the subject, you can read it here
Installation
composer require elhebert/laravel-sri
This package uses auto-discovery, so you don't have to do anything. It works out of the box.
Config
If you want to make changes in the configuration you can publish the config file using
php artisan vendor:publish --provider="Elhebert\SubresourceIntegrity\SriServiceProvider"
Content of the configuration
| key | default value | possible values |
|---|---|---|
| base_path | base_path('/public') |
|
| algorithm | sha256 | sha256, sha384 and sha512 |
| hashes | [] |
(see "How to get a hash) |
| mix_sri_path | public_path('mix-sri.json') |
(see "How to get a hash) |
| enabled | true |
|
| dangerously_allow_third_party_assets | false |
Usage
To only get a hash, use Sri::hash:
<link href="{{ asset('css/app.css') }}" rel="stylesheet" integrity="{{ Sri::hash('css/app.css') }}" crossorigin="anonymous" />
To generate the HTML for the integrity and the crossorigin attributes, use Sri::html. It accepts two parameters:
- first one is the path;
- second one (default is
false) tells if you want to pass the credentials when fetching the resource.
<link href="{{ asset('css/app.css') }}" rel="stylesheet" {{ Sri::html('css/app.css') }} />
Blade Component
Alternatively you can use blade components:
<x:sri.link href="css/app.css" rel="stylesheet" /> <!-- is the equivalent of doing --> <link href="{{ asset('css/app.css') }}" rel="stylesheet" integrity="{{ Sri::hash('css/app.css') }}" crossorigin="anonymous" />
If you add a mix attributet to the component it'll use mix() instead of asset() to generate the link to the assets:
<x:sri.link mix href="css/app.css" rel="stylesheet" /> <!-- is the equivalent of doing --> <link href="{{ mix('css/app.css') }}" rel="stylesheet" integrity="{{ Sri::hash('css/app.css') }}" crossorigin="anonymous" />
Improve performance
You should wrap your <link> and <script> tags with the @once directive to ensure that your tags are only rendered once. This will help with performances as it'll avoid a potential re-hashing of the files (in case you want to hash them on the fly).
Be careful that this should only be use for production as it won't re-render the html tag. Thus preventing new cache busting id to be added to the path by mix.
@once <link href="{{ mix('css/app.css') }}" rel="stylesheet" integrity="{{ Sri::hash('css/app.css') }}" crossorigin="anonymous" /> <!-- Or using the blade component --> <x:sri.link mix href="css/app.css" rel="stylesheet" /> @endonce
How to get a hash
Store hashes in the configuration
You can references the assets in the configuration like this:
[
// ...
'hashes' => [
'css/app.css' => 'my_super_hash'
'https://code.jquery.com/jquery-3.3.1.min.js' => 'sha256-FgpCb/KJQlLNfOu91ta32o/NMZxltwRo8QtmkMRdAu8='
]
]
This means, you have to calculate the hashes yourself. To do this, you can use report-uri.io, mozilla hash generator or any other resource available.
Using a webpack (or Mix) plugin to generate hashes on build
It expect a mix-sri.json file with a similar structure to the mix-manifest.json:
{
"/css/app.css": "my_super_hash",
"/js/app.js": "my_super_hash"
}
The filename and path can be changed in the configuration at any time.
Self promotion: I made a Laravel Mix extension laravel-mix-sri for this purpose.
Generate them on the fly
If it can't find the asset hash in the config file nor in the mix-sri.json file, it'll generate the hash on each reload of the page.
This method is the least recommended, because it reduce performance and make your page load slower.
Remote resources
This package also work for remote resources. Be careful that resources like Google Fonts won't work.
<script src="http://code.jquery.com/jquery-3.3.1.min.js" integrity="{{ Sri::hash('http://code.jquery.com/jquery-3.3.1.min.js') }}" crossorigin="anonymous" ></script> <!-- or with a blade component --> <x:sri.script src="http://code.jquery.com/jquery-3.3.1.min.js"></x:sri-script>
Contributing
Please see CONTRIBUTING for more details.
License
This project and the Laravel framework are open-sourced software licensed under the MIT license.
elhebert/laravel-sri 适用场景与选型建议
elhebert/laravel-sri 是一款 基于 PHP 开发的 Composer 扩展包,目前已累计 250.53k 次下载、GitHub Stars 达 39, 最近一次更新时间为 2018 年 02 月 01 日, 在 PHP 生态内属于活跃度较高的组件。
它主要适用于以下技术方向: 「sri」 「laravel-sri」 「subresource integrity」 等业务场景。在实际项目中,围绕这些方向常见需要落地的问题包括:接口对接、性能调优、并发安全、与既有框架(Laravel / ThinkPHP / Yii / Webman 等)的兼容适配,以及生产环境的日志埋点与稳定性保障。
我们在过去多个企业项目中使用过 elhebert/laravel-sri 或与其功能相近的方案,如果你在选型或落地过程中遇到问题,例如 版本兼容、二次改造、私有化封装、与内部系统对接、生产 BUG 排查,欢迎联系我们协助评估。
基于 elhebert/laravel-sri 在你已有业务上做功能扩展、字段裁剪、UI 适配、与内部账号 / 权限 / 日志系统的深度对接。
线上偶发问题、内存泄漏、慢查询、并发异常等排查修复;针对高流量场景做缓存、队列、索引层面的调优。
承接完整的项目从需求 → 设计 → 开发 → 上线 → 长期运维;也可按月提供技术保姆服务。
与 elhebert/laravel-sri 相关的其它包
同方向 / 同关键字的高下载量 PHP Composer 包推荐,方便对比选型:
CSS/Javascript Minificator, Compressor and Concatenator for TYPO3 - highly configurable frontend asset optimization for CSS/JS merging, minification and compression with optional body parsing, async/defer loading, inline output, data-ignore exclusions, SRI integrity validation/calculation, external
Subresource Integrity (SRI) package for Laravel
SRI Hash generator for laravel
Prefetch, Preconnect, DNS Prefetch, Preload, Prerender and Subresource helper
A package with some simple helpers for laravel and bootstrap
Subresource Integrity hash generator for laravel
统计信息
- 总下载量: 250.53k
- 月度下载量: 0
- 日度下载量: 0
- 收藏数: 39
- 点击次数: 32
- 依赖项目数: 0
- 推荐数: 0
其他信息
- 授权协议: MIT
- 更新时间: 2018-02-01