← Home

@esome-dev/sunflow-entity

22
Versions
MIT
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

heartyohcloud9316nalshya113

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata no-description AI (npm-metadata): Org-internal package; missing description is a consistent pattern, not a malice indicator. ai
provenance no-provenance AI (provenance): No provenance across all versions; consistent with org's publish workflow. ai
bogus-package bogus-package AI (bogus-package): Monorepo package with inflated semver matching sibling packages; not a spam/malware indicator for this publisher. ai
phantom-deps phantom-dep:@operato/shell AI (phantom-deps): Config-only reference in things-factory plugin framework; stable pattern across versions. ai
phantom-deps phantom-dep:@things-factory/integration-base AI (phantom-deps): Config-only reference in things-factory plugin framework; stable pattern across versions. ai
phantom-deps phantom-dep:@operato/graphql AI (phantom-deps): Config-only reference in things-factory plugin framework; stable pattern across versions. ai
phantom-deps phantom-dep:@things-factory/dataset AI (phantom-deps): Config-only reference in things-factory plugin framework; stable pattern across versions. ai

Versions (showing 22 of 22)

Version Deps Published
1.2.123 6 / 0
1.2.121 6 / 0
1.2.118 6 / 0
1.2.117 6 / 0
1.2.115 6 / 0
1.2.110 6 / 0
1.2.109 6 / 0
1.2.87 6 / 0
1.2.86 6 / 0
1.2.85 6 / 0
1.2.83 6 / 0
1.2.80 6 / 0
1.2.72 6 / 0
1.2.71 6 / 0
1.2.70 6 / 0
1.2.68 6 / 0
1.2.65 6 / 0
1.2.62 6 / 0
1.2.61 6 / 0
1.2.54 6 / 0
1.2.51 6 / 0
1.2.50 6 / 0

v1.2.123

2 findings
INFO No provenance attestation provenance

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

INFO Publisher changed: nalshya113 → cloud9316 (on 2026-07-03, known maintainer) provenance

This version was published by a different npm account (cloud9316) than the most recent previously approved version (nalshya113) on 2026-07-03, but cloud9316 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.