@classytic/media-kit
Engine-factory media management for Mongoose and Arc — arc-compatible events, dynamic multi-tenancy, pluggable storage drivers, smart pagination, image processing
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Org-managed publish-bot transition, consistent pattern, no compromise indicators. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Same bot account addition, benign org tooling transition. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.7.1 | 0 / 22 | |
| 3.7.0 | 0 / 22 | |
| 3.6.0 | 0 / 22 | |
| 3.5.0 | 0 / 22 | |
| 3.4.0 | 0 / 22 | |
| 3.3.1 | 0 / 21 | |
| 3.3.0 | 0 / 21 | |
| 3.2.0 | 0 / 21 | |
| 3.1.0 | 0 / 19 | |
| 3.0.0 | 0 / 18 | |
| 2.1.0 | 0 / 14 |
v3.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
2 findingsThis version was published by a different npm account than previous versions on 2026-07-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.