← Home

@sora-soft/account-cluster-template

npm Repository Homepage

sora system example

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

sora

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Template/example package from a small org; lack of Sigstore provenance is expected and not a risk signal here. ai
phantom-deps phantom-dep:mysql2 AI (phantom-deps): mysql2 is declared in dependencies and used via config/ORM layer; phantom-dep heuristic fires because it's not directly imported in source. ai

Versions (showing 9 of 9)

Version Deps Published
1.2.3 21 / 16
1.2.2 21 / 16
1.2.1 21 / 16
1.2.0 21 / 16
1.1.0 21 / 20
1.0.6 21 / 20
1.0.2 21 / 17
1.0.1 21 / 17
1.0.0 21 / 17

v1.2.3

1 finding
INFO No provenance attestation provenance

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

v1.2.2

1 finding
INFO No provenance attestation provenance

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

v1.2.1

1 finding
INFO No provenance attestation provenance

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

v1.2.0

1 finding
INFO No provenance attestation provenance

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

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

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

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