Gathering detailed insights and metrics for @tencent-serverless/tencent-website-beta
Gathering detailed insights and metrics for @tencent-serverless/tencent-website-beta
Installations
npm install @tencent-serverless/tencent-website-betaDeveloper Guide
BETA
Typescript
No
Module System
CommonJS
Node Version
12.6.0
NPM Version
6.12.0
Releases
14
Contributors
17
Unable to fetch Contributors
Languages
2
JavaScript
HTML
JavaScript (95.21%)
HTML (4.79%)
Developer
serverless-tencent
Download Statistics
Total Downloads
2,083
Last Day
1
Last Week
2
Last Month
17
Last Year
196
GitHub Statistics
83 Stars
205 Commits
15 Forks
11 Watching
3 Branches
17 Contributors
Bundle Size
10.39 MB
Minified
1.53 MB
Minified + Gzipped
Maintainers
2
Package Meta Information
Latest Version
1.2.19
Package Id
@tencent-serverless/tencent-website-beta@1.2.19
Unpacked Size
40.93 kB
Size
12.96 kB
File Count
14
NPM Version
6.12.0
Node Version
12.6.0
Total Downloads
Cumulative downloads
Total Downloads
2,083
Last day
0%
1
Compared to previous day
Last week
0%
2
Compared to previous week
Last month
142.9%
17
Compared to previous month
Last year
-54.7%
196
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Versions
Leverage this Serverless Component to deploy a website hosted on serverless infrastructure on Tencent within seconds. Easily add in your Vue.js, React.js or static assets and more.
1. Install
1$ npm install -g serverless
2. Create
1$ mkdir my-website 2$ cd my-website
Use the following command to create serverless.yml and .env files
1$ touch serverless.yml 2$ touch .env # your Tencent API Keys
Add the access keys of a Tencent CAM Role with AdministratorAccess in the .env file, using this format:
# .env
TENCENT_SECRET_ID=XXX
TENCENT_SECRET_KEY=XXX
Note: If you don't have a Tencent Cloud account, you could sign up first.
Move/Create your code in the folder, and the directory should look something like this:
|- code
|- index.html
|- serverless.yml
|- .env # your Tencent SecretId/Key/AppId
- If you don't have a Tencent Cloud account, you could sign up first.
Note: The code directory could either be a simple directory of html/css/js assets files, or a full fledged React app.
For this example, you could add the code to index.html file:
1<!DOCTYPE html> 2<html lang="en"> 3 <head> 4 <meta charset="UTF-8" /> 5 <title>Hello, Tencent Cloud</title> 6 </head> 7 <body> 8 Hello, Tencent Cloud 9 </body> 10</html>
3. Configure
1# serverless.yml 2 3myWebsite: 4 component: '@serverless/tencent-website' 5 inputs: 6 code: 7 src: ./code 8 index: index.html 9 error: index.html 10 region: ap-guangzhou 11 bucketName: my-bucket
4. Deploy
1$ sls --debug 2 3 DEBUG ─ Resolving the template's static variables. 4 DEBUG ─ Collecting components from the template. 5 DEBUG ─ Downloading any NPM components found in the template. 6 DEBUG ─ Analyzing the template's components dependencies. 7 DEBUG ─ Creating the template's components graph. 8 DEBUG ─ Syncing template state. 9 DEBUG ─ Executing the template's components graph. 10 DEBUG ─ Starting Website Component. 11 DEBUG ─ Preparing website Tencent COS bucket my-bucket-1300415943. 12 DEBUG ─ Deploying "my-bucket-1300415943" bucket in the "ap-guangzhou" region. 13 DEBUG ─ "my-bucket-1300415943" bucket was successfully deployed to the "ap-guangzhou" region. 14 DEBUG ─ Setting ACL for "my-bucket-1300415943" bucket in the "ap-guangzhou" region. 15 DEBUG ─ Ensuring no CORS are set for "my-bucket-1300415943" bucket in the "ap-guangzhou" region. 16 DEBUG ─ Ensuring no Tags are set for "my-bucket-1300415943" bucket in the "ap-guangzhou" region. 17 DEBUG ─ Configuring bucket my-bucket-1300415943 for website hosting. 18 DEBUG ─ Uploading website files from /Users/dfounderliu/Desktop/temp/code/src to bucket my-bucket-1300415943. 19 DEBUG ─ Starting upload to bucket my-bucket-1300415943 in region ap-guangzhou 20 DEBUG ─ Uploading directory /Users/dfounderliu/Desktop/temp/code/src to bucket my-bucket-1300415943 21 DEBUG ─ Website deployed successfully to URL: https://my-bucket-1300415943.cos-website.ap-guangzhou.myqcloud.com. 22 23 myWebsite: 24 url: https://my-bucket-1300415943.cos-website.ap-guangzhou.myqcloud.com 25 env: 26 27 2s › myWebsite › done 28 29
5. Remove
1$ sls remove --debug 2 3 DEBUG ─ Flushing template state and removing all components. 4 DEBUG ─ Starting Website Removal. 5 DEBUG ─ Removing Website bucket. 6 DEBUG ─ Removing files from the "my-bucket-1300415943" bucket. 7 DEBUG ─ Removing "my-bucket-1300415943" bucket from the "ap-guangzhou" region. 8 DEBUG ─ "my-bucket-1300415943" bucket was successfully removed from the "ap-guangzhou" region. 9 DEBUG ─ Finished Website Removal. 10 11 3s › myWebsite › done 12 13
New to Components?
Checkout the Serverless Components repo for more information.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 5/26 approved changesets -- score normalized to 1
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:15: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:20: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/release.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/release.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/test.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/test.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/validate.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/validate.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/validate.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/validate.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/validate.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/serverless-components/tencent-website/validate.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/release.yml:38
- Warn: npmCommand not pinned by hash: .github/workflows/release.yml:39
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:39
- Warn: npmCommand not pinned by hash: .github/workflows/test.yml:40
- Warn: npmCommand not pinned by hash: .github/workflows/validate.yml:39
- Warn: npmCommand not pinned by hash: .github/workflows/validate.yml:40
- Info: 0 out of 9 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 6 npmCommand dependencies pinned
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/release.yml:1
- Warn: no topLevel permission defined: .github/workflows/test.yml:1
- Warn: no topLevel permission defined: .github/workflows/validate.yml:1
- Info: no jobLevel write permissions found
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 16 are checked with a SAST tool
Score
3.5
/10
Last Scanned on 2024-12-16
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More