← Home

@bryntum/calendar-vue-3-thin

npm Homepage

Vue 3 wrappers for Bryntum Calendar JavaScript component

5
Versions
Commercial
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

mats.bryntserasmus.ersmarker

Keywords

bryntumcalendarvue-3wrapper

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff net-exec-file:src/components/BryntumTimeVisualizingEditorProps.ts AI (source-diff): File contains only TypeScript type declarations (import type / declare type); no runtime network or exec behavior. ai

Versions (showing 5 of 5)

Version Deps Published
7.2.4 0 / 0
7.2.3 0 / 0
7.1.3 0 / 0
7.1.2 0 / 0
7.1.1 0 / 0

v7.2.3

2 findings
HIGH New file with network + code execution: src/components/BryntumTimeVisualizingEditorProps.ts source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v7.1.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.1.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v7.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.