@zag-js/file-utils No license 10 versions

@zag-js/file-utils

npm Repository Homepage

10

Versions

—

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

Maintainers

segunadebayo

Keywords

jsutilsfile-utils

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/mime-types.js	AI (source-diff): MIME-type lookup table as compact string; not obfuscation. Stable for this package.	ai	2026/05/29
source-diff	obfuscated-file:dist/mime-types.mjs	AI (source-diff): ESM variant of same MIME-type table; not obfuscation.	ai	2026/05/29
source-diff	obfuscated-file:dist/mime-types.d.mts	AI (source-diff): Type declaration for MIME-type table string literal; not obfuscation.	ai	2026/05/29
source-diff	obfuscated-file:dist/mime-types.d.ts	AI (source-diff): Type declaration for MIME-type table string literal; not obfuscation.	ai	2026/05/29
source-diff	large-new-source-files	AI (source-diff): New MIME-type utility files added as part of package's file-utils purpose.	ai	2026/05/29
phantom-deps	phantom-dep:@zag-js/i18n-utils	AI (phantom-deps): Same-org monorepo sibling dep; phantom-dep false positive for this package.	ai	2026/04/29

Versions (showing 10 of 110)

Version	Deps	Published
1.3.3	1 / 1	2025-03-10
1.3.2	1 / 1	2025-03-08
1.3.1	1 / 1	2025-03-05
1.3.0	1 / 1	2025-03-03
1.2.1	1 / 1	2025-02-27
1.2.0	1 / 1	2025-02-26
1.1.0	1 / 1	2025-02-26
1.0.2	1 / 1	2025-02-24
1.0.1	1 / 1	2025-02-23
1.0.0	1 / 1	2025-02-22

v1.3.3

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

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

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

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.