@claspo/common No license 34 versions

@claspo/common

npm Homepage

34

Versions

—

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

claspo-devopsalex-chernysh

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:component-manifest/PropertyPaneManifest.interface.js	AI (source-diff): Package explicitly minifies all JS output via terser; minified files are expected and not obfuscation.	ai	2026/05/15
phantom-deps	phantom-dep:velocityjs	AI (phantom-deps): velocityjs is a declared runtime dep used via config files, not direct imports; stable false positive for this package.	ai	2026/05/15
bogus-package	bogus-package	AI (bogus-package): Sparse README reflects internal/org package style, not spam; 69 versions and active development confirm legitimacy.	ai	2026/05/15

Versions (showing 34 of 34)

Version	Deps	Published
7.3.0	1 / 12	2026-05-29
7.2.0	1 / 12	2026-05-01
7.1.5	1 / 12	2026-04-29
7.1.4	1 / 12	2026-04-20
7.1.3	1 / 12	2026-04-16
7.1.2	1 / 12	2026-04-14
7.1.1	1 / 12	2026-04-09
7.1.0	1 / 12	2026-04-07
7.0.8	1 / 12	2026-04-03
7.0.7	1 / 12	2026-04-02
7.0.6	1 / 12	2026-04-01
7.0.5	1 / 12	2026-03-31
7.0.4	1 / 12	2026-03-27
7.0.3	1 / 12	2026-03-25
7.0.2	1 / 12	2026-02-26
7.0.1	1 / 12	2026-02-26
7.0.0	1 / 12	2026-02-20
6.0.16	1 / 12	2026-02-13
6.0.15	1 / 12	2026-02-12
6.0.14	1 / 12	2026-02-06
6.0.13	1 / 12	2026-01-30
6.0.12	1 / 11	2026-01-27
6.0.11	1 / 11	2026-01-27
6.0.10	1 / 11	2026-01-27
6.0.9	1 / 11	2026-01-27
6.0.7	1 / 8	2026-01-23
6.0.6	1 / 8	2026-01-23
6.0.5	1 / 8	2026-01-23
6.0.4	1 / 8	2026-01-22
6.0.3	1 / 8	2026-01-21
6.0.2	1 / 8	2026-01-21
6.0.1	1 / 8	2026-01-21
6.0.0	1 / 8	2026-01-16
5.2.1	1 / 8	2026-01-09

v7.3.0

1 finding

LOW No provenance attestation provenance

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

v7.2.0

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.5

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.1.4

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.1.3

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.1.2

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.1.1

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.1.0

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.8

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.7

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.6

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.5

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.4

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.3

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.2

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.1

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v7.0.0

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.16

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.15

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.14

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.13

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.12

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.11

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.10

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.9

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.7

2 findings

HIGH New obfuscated file: component-manifest/PropertyPaneManifest.interface.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.

v6.0.6

1 finding

LOW No provenance attestation provenance

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

v6.0.5

1 finding

LOW No provenance attestation provenance

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

v6.0.4

1 finding

LOW No provenance attestation provenance

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

v6.0.3

1 finding

LOW No provenance attestation provenance

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

v6.0.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.

v6.0.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.

v6.0.0

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.

v5.2.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.