@absmartly/sdk-plugins
Collection of plugins for ABsmartly JavaScript SDK
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): setup-git-hooks.js is a dev-workflow script; scripts/ dir is excluded from published files, so it won't run for consumers. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is intentional in DOMManipulatorLite for A/B test DOM manipulation — core feature of this visual-editor SDK plugin. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.3.7 | 2 / 17 | |
| 1.3.6 | 2 / 17 | |
| 1.3.4 | 2 / 17 | |
| 1.3.0 | 1 / 17 | |
| 1.2.2 | 1 / 17 | |
| 1.2.1 | 1 / 17 | |
| 1.1.2 | 1 / 17 | |
| 1.1.1 | 1 / 17 | |
| 1.1.0 | 1 / 17 | |
| 1.0.1 | 0 / 17 |
v1.3.7
2 findingsScript: node scripts/setup-git-hooks.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.6
2 findingsScript: node scripts/setup-git-hooks.js
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
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.