Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump redocusaurus from 2.1.0 to 2.1.1 in /docs #3752

Merged
merged 1 commit into from
Jul 2, 2024

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 2, 2024

Bumps redocusaurus from 2.1.0 to 2.1.1.

Release notes

Sourced from redocusaurus's releases.

v2.1.1

redocusaurus@2.1.1

docusaurus-plugin-redoc@2.1.1

docusaurus-theme-redoc@2.1.1

Changelog

Sourced from redocusaurus's changelog.

redocusaurus@2.1.1

docusaurus-plugin-redoc@2.1.1

docusaurus-theme-redoc@2.1.1

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [redocusaurus](https://github.com/rohit-gohri/redocusaurus) from 2.1.0 to 2.1.1.
- [Release notes](https://github.com/rohit-gohri/redocusaurus/releases)
- [Changelog](https://github.com/rohit-gohri/redocusaurus/blob/main/CHANGELOG.md)
- [Commits](rohit-gohri/redocusaurus@v2.1.0...v2.1.1)

---
updated-dependencies:
- dependency-name: redocusaurus
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jul 2, 2024
@dependabot dependabot bot requested a review from a team as a code owner July 2, 2024 06:23
@dependabot dependabot bot added the javascript Pull requests that update Javascript code label Jul 2, 2024
Copy link
Contributor

@stacklokbot stacklokbot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependency Information

Minder analyzed the dependencies introduced in this pull request and detected that some dependencies do not meet your security profile.

📦 Dependency: @cfaester/enzyme-adapter-react-18

Trusty Score: 0

Scoring details
Component Score
Malicious false
Package activity 0
Provenance 0

📦 Dependency: @redocly/config

Trusty Score: 0

Scoring details
Component Score
From activity
Package activity 0
Provenance 5
Trust-summary 2.6
Malicious false
User activity 0
Repository activity 0

📦 Dependency: array-buffer-byte-length

Trusty Score: 4.2

Scoring details
Component Score
Provenance 5
Trust-summary 3.5
Malicious false
User activity 7.4
Repository activity 0.9
From activity
Package activity 4.2
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 2
Number of git tags or releases 2
Versions matched to tags or releases 2

📦 Dependency: array.prototype.filter

Trusty Score: 0

Scoring details
Component Score
Provenance 0
Malicious false
Package activity 0

📦 Dependency: arraybuffer.prototype.slice

Trusty Score: 4.2

Scoring details
Component Score
User activity 7.5
Repository activity 1
From activity
Package activity 4.2
Provenance 8
Trust-summary 4.2
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 4
Number of git tags or releases 4
Versions matched to tags or releases 2

📦 Dependency: available-typed-arrays

Trusty Score: 1.7

Scoring details
Component Score
Package activity 1.7
Provenance 8
Trust-summary 4.7
Malicious false
User activity 1.8
Repository activity 1.6
From activity
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 10
Number of git tags or releases 8
Versions matched to tags or releases 6

📦 Dependency: data-view-buffer

Trusty Score: 0

Scoring details
Component Score
Provenance 0
Malicious false
Package activity 0

📦 Dependency: data-view-byte-length

Trusty Score: 0

Scoring details
Component Score
Package activity 0
Provenance 0
Malicious false

📦 Dependency: data-view-byte-offset

Trusty Score: 4.1

Scoring details
Component Score
Trust-summary 2.6
Malicious false
User activity 7.4
Repository activity 0.8
From activity
Package activity 4.1
Provenance 5
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 1
Number of git tags or releases 1
Versions matched to tags or releases 1

📦 Dependency: discontinuous-range

Trusty Score: 3.7

Scoring details
Component Score
From activity
Package activity 3.7
Provenance 5
Trust-summary 2.9
Malicious false
User activity 5.4
Repository activity 1.9

📦 Dependency: enzyme-shallow-equal

Trusty Score: 0

Scoring details
Component Score
Malicious false
Package activity 0
Provenance 0

📦 Dependency: es-array-method-boxes-properly

Trusty Score: 4.2

Scoring details
Component Score
Provenance 5
Trust-summary 2.8
Malicious false
User activity 7.3
Repository activity 1.2
From activity
Package activity 4.2
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 1
Number of git tags or releases 1
Versions matched to tags or releases 1

📦 Dependency: es-object-atoms

Trusty Score: 3.9

Scoring details
Component Score
User activity 7.3
Repository activity 0.6
From activity
Package activity 3.9
Provenance 5
Trust-summary 1
Malicious false

📦 Dependency: es-set-tostringtag

Trusty Score: 4.3

Scoring details
Component Score
From activity
Package activity 4.3
Provenance 8
Trust-summary 4.4
Malicious false
User activity 7.5
Repository activity 1.1
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 5
Number of git tags or releases 5
Versions matched to tags or releases 4

📦 Dependency: es-shim-unscopables

Trusty Score: 4.1

Scoring details
Component Score
Malicious false
User activity 7.3
Repository activity 0.9
From activity
Package activity 4.1
Provenance 8
Trust-summary 4
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 3
Number of git tags or releases 3
Versions matched to tags or releases 1

📦 Dependency: es-to-primitive

Trusty Score: 4.8

Scoring details
Component Score
Package activity 4.8
Provenance 8
Trust-summary 5.3
Malicious false
User activity 7.5
Repository activity 2.1
From activity
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 6
Number of git tags or releases 6
Versions matched to tags or releases 6

📦 Dependency: function.prototype.name

Trusty Score: 4.8

Scoring details
Component Score
Trust-summary 5.2
Malicious false
User activity 7.5
Repository activity 2
From activity
Package activity 4.8
Provenance 8
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 11
Number of git tags or releases 11
Versions matched to tags or releases 9

📦 Dependency: functions-have-names

Trusty Score: 4.4

Scoring details
Component Score
User activity 7.4
Repository activity 1.4
From activity
Package activity 4.4
Provenance 8
Trust-summary 4.4
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 7
Number of git tags or releases 7
Versions matched to tags or releases 7

📦 Dependency: get-symbol-description

Trusty Score: 4.4

Scoring details
Component Score
Trust-summary 4.3
Malicious false
User activity 7.4
Repository activity 1.4
From activity
Package activity 4.4
Provenance 8
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 3
Number of git tags or releases 3
Versions matched to tags or releases 2

📦 Dependency: has-bigints

Trusty Score: 4.6

Scoring details
Component Score
Malicious false
User activity 7.4
Repository activity 1.8
From activity
Package activity 4.6
Provenance 8
Trust-summary 4.5
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 3
Number of git tags or releases 3
Versions matched to tags or releases 2

📦 Dependency: has-tostringtag

Trusty Score: 4.4

Scoring details
Component Score
Provenance 8
Trust-summary 4.3
Malicious false
User activity 7.4
Repository activity 1.5
From activity
Package activity 4.4
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 3
Number of git tags or releases 3
Versions matched to tags or releases 3

📦 Dependency: hasown

Trusty Score: 4

Scoring details
Component Score
User activity 7.4
Repository activity 0.7
From activity
Package activity 4
Provenance 8
Trust-summary 4.1
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 4
Number of git tags or releases 4
Versions matched to tags or releases 1

📦 Dependency: html-element-map

Trusty Score: 0

Scoring details
Component Score
Provenance 0
Malicious false
Package activity 0

📦 Dependency: internal-slot

Trusty Score: 4.3

Scoring details
Component Score
Repository activity 1.3
From activity
Package activity 4.3
Provenance 8
Trust-summary 4.4
Malicious false
User activity 7.3
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 8
Number of git tags or releases 8
Versions matched to tags or releases 6

📦 Dependency: is-array-buffer

Trusty Score: 4.6

Scoring details
Component Score
Malicious false
User activity 7.5
Repository activity 1.6
From activity
Package activity 4.6
Provenance 8
Trust-summary 4.5
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 10
Number of git tags or releases 10
Versions matched to tags or releases 7

📦 Dependency: is-bigint

Trusty Score: 4.6

Scoring details
Component Score
User activity 7.4
Repository activity 1.7
From activity
Package activity 4.6
Provenance 8
Trust-summary 4.7
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 5
Number of git tags or releases 5
Versions matched to tags or releases 4

📦 Dependency: is-boolean-object

Trusty Score: 4.5

Scoring details
Component Score
User activity 7.4
Repository activity 1.6
From activity
Package activity 4.5
Provenance 8
Trust-summary 4.5
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 5
Number of git tags or releases 5
Versions matched to tags or releases 4

📦 Dependency: is-data-view

Trusty Score: 0

Scoring details
Component Score
Malicious false
Package activity 0
Provenance 0

📦 Dependency: is-date-object

Trusty Score: 4.2

Scoring details
Component Score
Package activity 4.2
Provenance 8
Trust-summary 4.6
Malicious false
User activity 6.6
Repository activity 1.8
From activity
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 8
Number of git tags or releases 6
Versions matched to tags or releases 5

📦 Dependency: is-number-object

Trusty Score: 4.5

Scoring details
Component Score
Malicious false
User activity 7.4
Repository activity 1.7
From activity
Package activity 4.5
Provenance 8
Trust-summary 4.6
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 8
Number of git tags or releases 8
Versions matched to tags or releases 5

📦 Dependency: is-shared-array-buffer

Trusty Score: 1

Scoring details
Component Score
Trust-summary 3
Malicious false
User activity 7.4
Repository activity 1.4
From provenance
Package activity 4.4
Provenance 1

📦 Dependency: is-string

Trusty Score: 4.6

Scoring details
Component Score
Provenance 8
Trust-summary 3.1
Typosquatting ⚠️ Dependency may be trying to impersonate a well known package
Malicious false
User activity 7.4
Repository activity 1.8
From activity
Package activity 4.6
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 7
Number of git tags or releases 8
Versions matched to tags or releases 7

📦 Dependency: is-subset

Trusty Score: 2.7

Scoring details
Component Score
User activity 3.2
Repository activity 2.2
From activity
Package activity 2.7
Provenance 5
Trust-summary 3.1
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 2
Number of git tags or releases 2
Versions matched to tags or releases 2

📦 Dependency: is-symbol

Trusty Score: 4.2

Scoring details
Component Score
User activity 6.6
Repository activity 1.9
From activity
Package activity 4.2
Provenance 8
Trust-summary 4.6
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 7
Number of git tags or releases 5
Versions matched to tags or releases 4

📦 Dependency: is-typed-array

Trusty Score: 4.8

Scoring details
Component Score
Provenance 8
Trust-summary 4.7
Malicious false
User activity 7.5
Repository activity 2
From activity
Package activity 4.8
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 19
Number of git tags or releases 19
Versions matched to tags or releases 14

📦 Dependency: is-weakref

Trusty Score: 4.4

Scoring details
Component Score
Package activity 4.4
Provenance 8
Trust-summary 4.2
Malicious false
User activity 7.4
Repository activity 1.4
From activity
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 3
Number of git tags or releases 3
Versions matched to tags or releases 1

📦 Dependency: lodash.escape

Trusty Score: 1

Scoring details
Component Score
Provenance 1
Trust-summary 3.3
Malicious false
User activity 8.6
Repository activity 8.7
From provenance
Package activity 8.7

📦 Dependency: lodash.flattendeep

Trusty Score: 1

Scoring details
Component Score
Repository activity 8.7
From provenance
Package activity 8.6
Provenance 1
Trust-summary 3.2
Malicious false
User activity 8.6

📦 Dependency: nearley

Trusty Score: 1

Scoring details
Component Score
User activity 6.2
Repository activity 6.3
From provenance
Package activity 6.2
Provenance 1
Trust-summary 3.6
Malicious false

📦 Dependency: object.entries

Trusty Score: 4.9

Scoring details
Component Score
Provenance 8
Trust-summary 5
Malicious false
User activity 7.5
Repository activity 2.3
From activity
Package activity 4.9
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 14
Number of git tags or releases 14
Versions matched to tags or releases 12

📦 Dependency: object.values

Trusty Score: 2.2

Scoring details
Component Score
From activity
Package activity 2.2
Provenance 8
Trust-summary 3.8
Typosquatting ⚠️ Dependency may be trying to impersonate a well known package
Malicious false
User activity 2.1
Repository activity 2.3
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 15
Number of git tags or releases 13
Versions matched to tags or releases 7

📦 Dependency: performance-now

Trusty Score: 0.6

Scoring details
Component Score
Malicious false
User activity 0
Repository activity 1.1
From activity
Package activity 0.6
Provenance 5
Trust-summary 3.3

📦 Dependency: possible-typed-array-names

Trusty Score: 0

Scoring details
Component Score
Malicious false
Package activity 0
Provenance 0

📦 Dependency: rst-selector-parser

Trusty Score: 0

Scoring details
Component Score
Package activity 0
Provenance 0
Malicious false

📦 Dependency: safe-array-concat

Trusty Score: 4.3

Scoring details
Component Score
Provenance 8
Trust-summary 3.9
Malicious false
User activity 7.3
Repository activity 1.3
From activity
Package activity 4.3
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 5
Number of git tags or releases 5
Versions matched to tags or releases 4

📦 Dependency: safe-regex-test

Trusty Score: 4.4

Scoring details
Component Score
User activity 7.4
Repository activity 1.4
From activity
Package activity 4.4
Provenance 8
Trust-summary 4.7
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 4
Number of git tags or releases 4
Versions matched to tags or releases 4

📦 Dependency: set-function-name

Trusty Score: 4.5

Scoring details
Component Score
Malicious false
User activity 7.8
Repository activity 1.3
From activity
Package activity 4.5
Provenance 8
Trust-summary 4
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 5
Number of git tags or releases 3
Versions matched to tags or releases 2

📦 Dependency: string.prototype.trim

Trusty Score: 4.9

Scoring details
Component Score
Package activity 4.9
Provenance 8
Trust-summary 5.5
Malicious false
User activity 7.8
Repository activity 2
From activity
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 14
Number of git tags or releases 14
Versions matched to tags or releases 11

📦 Dependency: string.prototype.trimend

Trusty Score: 4.7

Scoring details
Component Score
Provenance 8
Trust-summary 4.6
Malicious false
User activity 7.6
Repository activity 1.8
From activity
Package activity 4.7
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 11
Number of git tags or releases 11
Versions matched to tags or releases 7

📦 Dependency: string.prototype.trimstart

Trusty Score: 4.7

Scoring details
Component Score
From activity
Package activity 4.7
Provenance 8
Trust-summary 4.6
Malicious false
User activity 7.6
Repository activity 1.8
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 11
Number of git tags or releases 11
Versions matched to tags or releases 7

📦 Dependency: typed-array-buffer

Trusty Score: 1.4

Scoring details
Component Score
User activity 1.8
Repository activity 1
From activity
Package activity 1.4
Provenance 8
Trust-summary 4.2
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 5
Number of git tags or releases 3
Versions matched to tags or releases 2

📦 Dependency: typed-array-byte-length

Trusty Score: 4

Scoring details
Component Score
Provenance 5
Trust-summary 3.4
Malicious false
User activity 7.4
Repository activity 0.6
From activity
Package activity 4
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 2
Number of git tags or releases 2
Versions matched to tags or releases 1

📦 Dependency: typed-array-byte-offset

Trusty Score: 4.1

Scoring details
Component Score
Provenance 8
Trust-summary 4.1
Malicious false
User activity 7.4
Repository activity 0.9
From activity
Package activity 4.1
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 3
Number of git tags or releases 3
Versions matched to tags or releases 2

📦 Dependency: typed-array-length

Trusty Score: 4.4

Scoring details
Component Score
Malicious false
User activity 7.4
Repository activity 1.4
From activity
Package activity 4.4
Provenance 8
Trust-summary 4.5
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 7
Number of git tags or releases 7
Versions matched to tags or releases 5

📦 Dependency: unbox-primitive

Trusty Score: 4.5

Scoring details
Component Score
Malicious false
User activity 7.5
Repository activity 1.4
From activity
Package activity 4.5
Provenance 8
Trust-summary 4.1
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 3
Number of git tags or releases 3
Versions matched to tags or releases 2

📦 Dependency: which-boxed-primitive

Trusty Score: 4.6

Scoring details
Component Score
User activity 7.5
Repository activity 1.6
From activity
Package activity 4.6
Provenance 8
Trust-summary 4.1
Malicious false
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 3
Number of git tags or releases 3
Versions matched to tags or releases 3

📦 Dependency: which-typed-array

Trusty Score: 4.7

Scoring details
Component Score
Repository activity 1.8
From activity
Package activity 4.7
Provenance 8
Trust-summary 4.7
Malicious false
User activity 7.5
Proof of Origin (Provenance)

This package can be linked back to its source code using a historical provenance map.

We were able to correlate a significant number of git tags and tagged releases in this package’s source code to versions of the published package. This mapping creates a strong link from the package back to its source code repository, verifying proof of origin.

Published package versions 18
Number of git tags or releases 18
Versions matched to tags or releases 13

@coveralls
Copy link

Coverage Status

coverage: 51.997%. remained the same
when pulling b5df2a8 on dependabot/npm_and_yarn/docs/redocusaurus-2.1.1
into 5d519d3 on main.

@jhrozek jhrozek merged commit 34acceb into main Jul 2, 2024
20 checks passed
@jhrozek jhrozek deleted the dependabot/npm_and_yarn/docs/redocusaurus-2.1.1 branch July 2, 2024 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants