@intuned/runtime
Intuned runtime
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:ms | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Config-referenced; typical for framework-aware runtime packages. | ai | |
| phantom-deps | phantom-dep:fastify | AI (phantom-deps): Config-referenced; typical for framework-aware runtime packages. | ai | |
| phantom-deps | phantom-dep:file-type | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:playwright | AI (phantom-deps): Config-referenced; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:read-chunk | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:async-retry | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:stack-utils | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@tinyhttp/app | AI (phantom-deps): Config-referenced; typical for framework-aware runtime packages. | ai | |
| phantom-deps | phantom-dep:playwright-extra | AI (phantom-deps): Config-referenced; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:https-proxy-agent | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:zod-validation-error | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:press-any-key | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:terminal-link | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Config-referenced dependency; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:babel-plugin-dynamic-import-node | AI (phantom-deps): Config-referenced babel plugin; stable for this package. | ai | |
| phantom-deps | phantom-dep:@babel/plugin-syntax-dynamic-import | AI (phantom-deps): Framework-scoped babel plugin; convention-loaded. | ai | |
| phantom-deps | phantom-dep:@types/fs-extra | AI (phantom-deps): Framework-scoped type package; convention-loaded. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): Known implicit runtime dependency; stable pattern. | ai | |
| phantom-deps | phantom-dep:which | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:ignore | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:prompts | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Config-referenced build tool; stable for this package. | ai | |
| phantom-deps | phantom-dep:promptly | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:image-size | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Framework-scoped type package; convention-loaded. | ai | |
| phantom-deps | phantom-dep:milliparsec | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:terminal-kit | AI (phantom-deps): Config-referenced; stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/lodash | AI (phantom-deps): Framework-scoped type package; convention-loaded. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 1.3.28 | 44 / 38 | |
| 1.3.27 | 44 / 38 | |
| 1.3.26 | 44 / 38 | |
| 1.3.25 | 44 / 38 | |
| 1.3.24 | 44 / 38 | |
| 1.3.23 | 44 / 38 | |
| 1.3.22 | 44 / 38 | |
| 1.3.21 | 43 / 38 | |
| 1.3.20 | 43 / 38 | |
| 1.3.19 | 43 / 38 | |
| 1.3.18 | 43 / 38 | |
| 1.3.17 | 44 / 35 | |
| 1.3.16 | 43 / 35 | |
| 1.3.15 | 43 / 35 | |
| 1.3.14 | 42 / 35 | |
| 1.3.13 | 42 / 35 | |
| 1.3.12 | 42 / 35 | |
| 1.3.11 | 42 / 35 | |
| 1.3.10 | 40 / 34 | |
| 1.3.9 | 40 / 34 | |
| 1.3.7 | 41 / 34 | |
| 1.3.6 | 41 / 34 | |
| 1.3.5 | 41 / 34 | |
| 1.3.3 | 38 / 34 | |
| 1.1.5 | 36 / 31 | |
| 1.1.4 | 36 / 31 | |
| 1.1.2 | 38 / 31 | |
| 1.1.1 | 38 / 31 | |
| 1.1.0 | 49 / 31 |
v1.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.