papaparse

Build provenancecaution

No build attestation or trusted-publisher provenance is available, leaving publication origin less independently verifiable. This lowers transparency but is offset by the active, matching source repository and consistent release documentation.

Repo toolingcaution

The repository uses build tooling, but no security-scanning tools were detected. The missing scanning is a modest security-hygiene gap, while the build setup itself supports reproducible project maintenance.

Security policycaution

The repository has no published security policy, so vulnerability reporting and response expectations are less transparent. This is a documentation gap, not evidence that the project is abandoned.

Token permissionscaution

The only workflow lacks a top-level permissions declaration, so its GitHub token permissions are not explicitly minimized. No top-level write permissions were detected, limiting the severity of this hygiene concern.

Type declarationscaution

No type declarations are published, which can reduce convenience and safety for TypeScript consumers of this library. This is a consumer-ergonomics gap rather than evidence of abandonment.