@orion-js/typed-model
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@orion-js/services | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive for transitive/re-exported usage. | ai | |
| phantom-deps | phantom-dep:@orion-js/resolvers | AI (phantom-deps): Same-org monorepo dep; phantom-dep heuristic false positive for transitive/re-exported usage. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 4.3.1 | 4 / 3 | |
| 4.3.0 | 4 / 3 | |
| 4.2.1 | 4 / 4 | |
| 4.2.0 | 4 / 4 | |
| 4.1.7 | 4 / 4 | |
| 4.1.6 | 4 / 4 | |
| 4.1.5 | 4 / 4 | |
| 4.1.4 | 4 / 4 | |
| 4.1.3 | 4 / 4 | |
| 4.1.2 | 4 / 4 | |
| 4.1.1 | 4 / 4 | |
| 4.1.0 | 4 / 4 | |
| 4.0.19 | 4 / 4 | |
| 4.0.18 | 4 / 4 | |
| 4.0.17 | 4 / 4 | |
| 4.0.16 | 4 / 4 | |
| 4.0.15 | 4 / 4 | |
| 4.0.14 | 4 / 4 |
v4.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.