← Home

@satorijs/element

npm Repository Homepage
11
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

shigmacordis-bot

Keywords

satorielementsegmentcomponentmessageutilities

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:new-function-constructor AI (semgrep): Used to build a sandboxed expression evaluator for JSX/template context — a legitimate and documented pattern in this message element library. Not obfuscated or malicious. ai
dependencies unvetted-dep:cosmokit AI (dependencies): cosmokit is a utility library from the same Satori/Koishi ecosystem and author (Shigma); stable dependency with no known issues. ai

Versions (showing 11 of 11)

Version Deps Published
3.2.0 1 / 3
3.1.8 1 / 3
3.1.7 1 / 1
3.1.6 1 / 1
3.1.5 1 / 1
3.1.4 1 / 1
3.1.3 1 / 1
3.1.2 1 / 1
3.1.1 1 / 1
3.1.0 1 / 2
3.0.0 1 / 1

v3.1.7

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.

v3.1.6

1 finding
LOW No provenance attestation provenance

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

v3.1.5

1 finding
LOW No provenance attestation provenance

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

v3.1.4

1 finding
LOW No provenance attestation provenance

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

v3.1.3

1 finding
LOW No provenance attestation provenance

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

v3.1.2

1 finding
LOW No provenance attestation provenance

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

v3.1.1

1 finding
LOW No provenance attestation provenance

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

v3.1.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.

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