@jrmc/adonis-attachment
Turn any field on your Lucid model to an attachment data type
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Provenance is a best-practice signal, not a security blocker; stable for this package. | ai | |
| dependencies | unvetted-dep:exifreader | AI (dependencies): Legitimate EXIF parsing library; expected dependency for an attachment/image handling package. | ai | |
| dependencies | unvetted-dep:@verrou/core | AI (dependencies): AdonisJS ecosystem locking library; appropriate for attachment concurrency control. | ai | |
| dependencies | unvetted-dep:@poppinss/defer | AI (dependencies): Poppinss utility used across AdonisJS ecosystem; stable false positive for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.2.0 | 7 / 29 | |
| 5.1.5 | 7 / 29 | |
| 5.1.4 | 7 / 29 | |
| 5.1.3 | 7 / 29 | |
| 5.1.2 | 7 / 29 | |
| 5.1.1 | 7 / 29 | |
| 5.1.0 | 7 / 29 | |
| 5.0.5 | 7 / 29 | |
| 5.0.4 | 7 / 29 | |
| 5.0.3 | 7 / 29 | |
| 5.0.2 | 7 / 29 | |
| 5.0.1 | 7 / 29 | |
| 5.0.0 | 7 / 29 |
v5.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.