@seafile/seafile-calendar
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/rc-calendar.js | AI (source-diff): Standard webpack UMD bundle; long lines are minified output, not obfuscation. | ai | |
| source-diff | net-exec-file:dist/rc-calendar.js | AI (source-diff): Webpack bootstrap pattern; no actual network calls or dynamic code execution beyond module loading. | ai | |
| source-diff | net-exec-file:dist/rc-calendar.min.js | AI (source-diff): Minified webpack bundle; same pattern as rc-calendar.js, no malicious network/exec behavior. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 1.0.11 | 7 / 18 | |
| 1.0.10 | 7 / 18 | |
| 1.0.9 | 7 / 18 | |
| 1.0.8 | 7 / 18 | |
| 1.0.7 | 7 / 18 | |
| 1.0.6 | 7 / 18 | |
| 1.0.5 | 7 / 18 | |
| 1.0.4 | 7 / 18 | |
| 1.0.3 | 7 / 18 | |
| 1.0.2 | 7 / 18 | |
| 1.0.1 | 7 / 18 | |
| 1.0.0 | 7 / 18 | |
| 0.1.3 | 7 / 18 |
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.