@appland/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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Sparse metadata is a consistent pattern across all 79 versions of this established @appland org package, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): No description is a stable characteristic of this package across all versions; not a risk signal here. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 2.10.4 | 2 / 14 | |
| 2.10.3 | 2 / 14 | |
| 2.10.2 | 2 / 15 | |
| 2.10.1 | 2 / 15 | |
| 2.10.0 | 2 / 15 | |
| 2.9.0 | 2 / 15 | |
| 2.8.0 | 2 / 14 | |
| 2.7.0 | 2 / 14 | |
| 2.6.5 | 2 / 13 | |
| 2.6.4 | 2 / 13 | |
| 2.6.3 | 2 / 13 | |
| 2.6.2 | 2 / 12 | |
| 2.6.1 | 2 / 12 | |
| 2.6.0 | 2 / 12 | |
| 2.5.0 | 2 / 12 | |
| 2.4.3 | 2 / 12 | |
| 2.4.2 | 2 / 12 | |
| 2.4.1 | 2 / 12 | |
| 2.4.0 | 2 / 12 | |
| 2.3.0 | 2 / 12 | |
| 2.2.1 | 2 / 12 | |
| 2.2.0 | 2 / 12 | |
| 2.1.0 | 2 / 12 | |
| 2.0.0 | 2 / 12 |
v2.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.