@nocobase/plugin-logger Apache-2.0 51 versions

@nocobase/plugin-logger

npm Homepage

Server-side logs, mainly including API request logs and system runtime logs, and allows to package and download log files.

51

Versions

Apache-2.0

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

chenosjiannlu

Keywords

Logging and monitoring

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/client/cadb8b365e6b852a.js	AI (source-diff): NocoBase plugins ship webpack-bundled client chunks with content-hash filenames. The sample confirms standard webpack chunk format with NocoBase copyright header — minified, not malicious.	ai	2026/04/27
source-diff	obfuscated-file:dist/client/726.3980df72fcd7dc1d.js	AI (source-diff): NocoBase ships webpack-minified client bundles in all versions; long lines are standard webpack output with copyright headers, not malicious obfuscation.	ai	2026/04/26
source-diff	obfuscated-file:dist/client/2cf10c4f93299e14.js	AI (source-diff): Standard webpack-minified client bundle for a NocoBase plugin. Copyright header and chunk format confirm legitimate build output; not malicious obfuscation.	ai	2026/04/26
bogus-package	bogus-package	AI (bogus-package): NocoBase plugins consistently use documentation-link READMEs pointing to their docs site. Not a spam/phishing pattern for this established ecosystem package.	ai	2026/04/26

Versions (showing 51 of 125)

View all versions

Version	Deps	Published
2.0.61	0 / 2	2026-06-03
2.0.60	0 / 2	2026-05-29
2.0.59	0 / 2	2026-05-28
2.0.58	0 / 2	2026-05-28
2.0.57	0 / 2	2026-05-25
2.0.56	0 / 2	2026-05-21
2.0.55	0 / 2	2026-05-18
2.0.54	0 / 2	2026-05-15
2.0.53	0 / 2	2026-05-14
2.0.52	0 / 2	2026-05-13
2.0.51	0 / 2	2026-05-10
2.0.50	0 / 2	2026-05-09
2.0.49	0 / 2	2026-05-06
2.0.48	0 / 2	2026-05-04
2.0.47	0 / 2	2026-05-01
2.0.46	0 / 2	2026-04-28
2.0.45	0 / 2	2026-04-27
2.0.44	0 / 2	2026-04-26
2.0.43	0 / 2	2026-04-24
2.0.42	0 / 2	2026-04-23
2.0.41	0 / 2	2026-04-22
2.0.40	0 / 2	2026-04-20
2.0.39	0 / 2	2026-04-17
2.0.38	0 / 2	2026-04-16
2.0.37	0 / 2	2026-04-14
2.0.36	0 / 2	2026-04-10
2.0.35	0 / 2	2026-04-09
2.0.34	0 / 2	2026-04-08
2.0.33	0 / 2	2026-04-08
2.0.32	0 / 2	2026-04-04
2.0.31	0 / 2	2026-04-01
2.0.30	0 / 2	2026-03-30
2.0.29	0 / 2	2026-03-29
2.0.28	0 / 2	2026-03-27
2.0.27	0 / 2	2026-03-26
2.0.26	0 / 2	2026-03-25
2.0.25	0 / 2	2026-03-23
2.0.24	0 / 2	2026-03-22
2.0.23	0 / 2	2026-03-20
2.0.22	0 / 2	2026-03-20
2.0.21	0 / 2	2026-03-20
2.0.20	0 / 2	2026-03-19
2.0.19	0 / 2	2026-03-17
2.0.18	0 / 2	2026-03-17
2.0.17	0 / 2	2026-03-14
2.0.16	0 / 2	2026-03-12
2.0.15	0 / 2	2026-03-12
2.0.14	0 / 2	2026-03-11
2.0.13	0 / 2	2026-03-10
2.0.12	0 / 2	2026-03-09
2.0.11	0 / 2	2026-03-06

v2.0.61

1 finding

LOW No provenance attestation provenance

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

v2.0.60

1 finding

LOW No provenance attestation provenance

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

v2.0.59

1 finding

LOW No provenance attestation provenance

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

v2.0.58

1 finding

LOW No provenance attestation provenance

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

v2.0.57

1 finding

LOW No provenance attestation provenance

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

v2.0.56

1 finding

LOW No provenance attestation provenance

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

v2.0.55

1 finding

LOW No provenance attestation provenance

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

v2.0.54

1 finding

LOW No provenance attestation provenance

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

v2.0.53

1 finding

LOW No provenance attestation provenance

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

v2.0.52

1 finding

LOW No provenance attestation provenance

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

v2.0.51

1 finding

LOW No provenance attestation provenance

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

v2.0.50

1 finding

LOW No provenance attestation provenance

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

v2.0.49

1 finding

LOW No provenance attestation provenance

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

v2.0.48

1 finding

LOW No provenance attestation provenance

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

v2.0.47

1 finding

LOW No provenance attestation provenance

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

v2.0.45

1 finding

LOW No provenance attestation provenance

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

v2.0.44

1 finding

LOW No provenance attestation provenance

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

v2.0.43

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.

v2.0.42

2 findings

HIGH New obfuscated file: dist/client/726.3980df72fcd7dc1d.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.41

2 findings

HIGH New obfuscated file: dist/client/726.3980df72fcd7dc1d.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.40

2 findings

HIGH New obfuscated file: dist/client/726.3980df72fcd7dc1d.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.39

2 findings

HIGH New obfuscated file: dist/client/726.3980df72fcd7dc1d.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.38

1 finding

LOW No provenance attestation provenance

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

v2.0.37

1 finding

LOW No provenance attestation provenance

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

v2.0.36

1 finding

LOW No provenance attestation provenance

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

v2.0.35

1 finding

LOW No provenance attestation provenance

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

v2.0.34

1 finding

LOW No provenance attestation provenance

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

v2.0.33

1 finding

LOW No provenance attestation provenance

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

v2.0.32

1 finding

LOW No provenance attestation provenance

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

v2.0.31

1 finding

LOW No provenance attestation provenance

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

v2.0.30

1 finding

LOW No provenance attestation provenance

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

v2.0.29

1 finding

LOW No provenance attestation provenance

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

v2.0.28

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.

v2.0.27

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.

v2.0.26

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.

v2.0.25

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.24

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.23

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.22

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.21

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.20

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.19

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.18

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.17

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.16

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.15

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.14

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.13

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.12

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v2.0.11

2 findings

HIGH New obfuscated file: dist/client/cadb8b365e6b852a.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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