@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, so a manually published version cannot be tied back to a reviewed commit.
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 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 8.16.0 | 6 / 12 | |
| 8.15.1 | 6 / 12 | |
| 8.15.0 | 6 / 12 | |
| 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 | |
| 8.8.3 | 7 / 12 | |
| 8.8.2 | 7 / 12 | |
| 8.8.1 | 7 / 12 | |
| 8.8.0 | 7 / 12 | |
| 8.7.0 | 5 / 10 | |
| 8.6.0 | 5 / 10 |
v8.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.