← Home

@esome-dev/sunflow-entity

npm Repository
20
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 — the axios compromise (March 2026) relied on exactly this gap.

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 20 of 20)

Version Deps Published
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.118

1 finding
LOW No provenance attestation provenance

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

v1.2.117

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

1 finding
LOW No provenance attestation provenance

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

v1.2.110

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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.