← Home

@sora-soft/framework

npm Repository Homepage

sora system framework project

9
Versions
WTFPL
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

q619389112xyyaya

Keywords

soraframe

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@sora-soft/define-transform AI (phantom-deps): Same-org scoped transform dep; likely consumed indirectly at build/runtime via typia transform pipeline. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Standard Proxy/Reflect pattern for method binding; not obfuscation in this context. ai
phantom-deps phantom-dep:@sora-soft/typia-decorator AI (phantom-deps): Same org scope, listed as runtime dependency; phantom-dep heuristic is a false positive here. ai

Versions (showing 9 of 9)

Version Deps Published
2.2.2 8 / 15
2.2.1 8 / 15
2.2.0 7 / 15
2.1.0 7 / 18
2.0.4 7 / 18
2.0.3 7 / 18
2.0.2 7 / 14
2.0.1 7 / 12
2.0.0 7 / 12

v2.2.2

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

1 finding
LOW No provenance attestation provenance

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

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