← Home

@opengis/fastify-file

npm
31
Versions
—
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

evheniihavryliukandrii.cherinsetebosurapax.deusmchernenkonikachu404serebasikkoleksandr_krizhanovskyaponaskofarizov_maximbohdana_usenko

Keywords

fastifyfileconvertgrpcs3

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@grpc/proto-loader AI (phantom-deps): gRPC proto-loader loaded by convention; stable false positive. ai
phantom-deps phantom-dep:image-size AI (phantom-deps): Utility dep referenced in config; stable false positive for this package. ai
phantom-deps phantom-dep:@grpc/grpc-js AI (phantom-deps): gRPC dep loaded by convention per config; stable false positive. ai
phantom-deps phantom-dep:@aws-sdk/client-s3 AI (phantom-deps): AWS SDK loaded by convention; stable false positive for this package. ai
phantom-deps phantom-dep:formidable AI (phantom-deps): Framework-scoped optional dependency loaded by convention; stable false positive for this package. ai
phantom-deps phantom-dep:fastify AI (phantom-deps): fastify is a peer dependency in a fastify plugin; not directly imported but used via plugin registration. ai
phantom-deps phantom-dep:undici AI (phantom-deps): undici is a known implicit runtime dependency of fastify; stable false positive for fastify plugins. ai
semgrep semgrep:base64-decode AI (semgrep): Base64 decode is used to write uploaded file content to disk — standard file upload handling, not obfuscation. ai

Versions (showing 31 of 31)

Version Deps Published
1.0.86 9 / 2
1.0.85 9 / 2
1.0.84 9 / 10
1.0.83 9 / 10
1.0.82 9 / 10
1.0.81 9 / 10
1.0.80 9 / 10
1.0.79 9 / 10
1.0.78 9 / 10
1.0.77 9 / 10
1.0.76 9 / 10
1.0.64 9 / 10
1.0.63 9 / 10
1.0.62 9 / 10
1.0.61 9 / 10
1.0.60 9 / 10
1.0.59 9 / 10
1.0.58 9 / 10
1.0.57 9 / 10
1.0.21 8 / 2
1.0.20 8 / 2
1.0.19 8 / 2
1.0.18 8 / 2
1.0.17 8 / 2
1.0.16 8 / 2
1.0.15 8 / 2
1.0.14 8 / 2
1.0.13 8 / 2
1.0.12 8 / 2
1.0.11 8 / 2
1.0.10 8 / 2

v1.0.79

1 finding
LOW No provenance attestation provenance

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

v1.0.78

1 finding
LOW No provenance attestation provenance

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

v1.0.77

1 finding
LOW No provenance attestation provenance

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

v1.0.64

2 findings
HIGH New maintainer(s) added: aponasko maintainer-change

[Reject — re-review on republish] (prior reject: AI (maintainer-change): New maintainers added alongside a 99% source size drop; pattern consistent with account takeover or malicious replacement.) Maintainer list changed between previously vetted version and this version. New maintainers could indicate a legitimate transfer or a potential account compromise.

LOW No provenance attestation provenance

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

v1.0.63

1 finding
LOW No provenance attestation provenance

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

v1.0.62

1 finding
LOW No provenance attestation provenance

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

v1.0.61

1 finding
LOW No provenance attestation provenance

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

v1.0.60

1 finding
LOW No provenance attestation provenance

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

v1.0.59

1 finding
LOW No provenance attestation provenance

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

v1.0.58

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

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

1 finding
LOW No provenance attestation provenance

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

v1.0.20

1 finding
LOW No provenance attestation provenance

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

v1.0.19

1 finding
LOW No provenance attestation provenance

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

v1.0.18

1 finding
LOW No provenance attestation provenance

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

v1.0.17

1 finding
LOW No provenance attestation provenance

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

v1.0.16

1 finding
LOW No provenance attestation provenance

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

v1.0.15

1 finding
LOW No provenance attestation provenance

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

v1.0.14

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: andrii.cherin → setebosu (on 2024-05-17, known maintainer) provenance

This version was published by a different npm account (setebosu) than the most recent previously approved version (andrii.cherin) on 2024-05-17, but setebosu 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.

v1.0.13

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: andrii.cherin → setebosu (on 2024-05-16, known maintainer) provenance

This version was published by a different npm account (setebosu) than the most recent previously approved version (andrii.cherin) on 2024-05-16, but setebosu 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.

v1.0.12

1 finding
LOW No provenance attestation provenance

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

v1.0.11

1 finding
LOW No provenance attestation provenance

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

v1.0.10

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.