← Home

@tachybase/module-file

npm Repository Homepage

Provides files storage services with files collection template and attachment field.

22
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

sealdaytomyjan

Keywords

CollectionsCollection fields

Versions (showing 22 of 22)

Version Deps Published
1.6.24 0 / 22
1.6.23 0 / 22
1.6.22 0 / 22
1.6.21 0 / 21
1.6.20 0 / 21
1.6.19 0 / 21
1.6.18 0 / 21
1.6.17 0 / 21
1.6.16 0 / 21
1.6.15 0 / 21
1.6.14 0 / 21
1.6.7 0 / 21
1.6.6 0 / 21
1.6.5 0 / 21
1.6.4 0 / 21
1.6.3 0 / 21
1.6.2 0 / 21
1.6.1 0 / 21
1.6.0 0 / 21
1.5.1 0 / 21
1.5.0 0 / 21
1.4.0 0 / 21

v1.6.24

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.23

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.6.7

1 finding
LOW No provenance attestation provenance

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

v1.6.6

1 finding
LOW No provenance attestation provenance

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

v1.6.5

1 finding
LOW No provenance attestation provenance

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

v1.6.4

1 finding
LOW No provenance attestation provenance

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

v1.6.3

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: tomyjan → sealday (on 2025-12-26, known maintainer) provenance

This version was published by a different npm account (sealday) than the most recent previously approved version (tomyjan) on 2025-12-26, but sealday 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.6.2

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: sealday → tomyjan (on 2025-12-22, known maintainer) provenance

This version was published by a different npm account (tomyjan) than the most recent previously approved version (sealday) on 2025-12-22, but tomyjan 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.6.1

1 finding
LOW No provenance attestation provenance

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

v1.6.0

1 finding
LOW No provenance attestation provenance

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

v1.5.1

1 finding
LOW No provenance attestation provenance

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

v1.5.0

1 finding
LOW No provenance attestation provenance

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

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