@janiscommerce/model
A package for managing Janis Models
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Driver-loader pattern requiring @janiscommerce/{type}; stable and intentional across versions of this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.14.0 | 6 / 12 | |
| 8.13.0 | 6 / 12 | |
| 8.12.1 | 6 / 12 | |
| 8.12.0 | 6 / 12 | |
| 8.11.0 | 7 / 12 | |
| 8.10.0 | 7 / 12 | |
| 8.9.0 | 7 / 12 |
v8.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.