@aptre/common
Common project configuration files and dependencies.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): Config/tooling dependency; stable pattern for this shared-config package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unused-imports | AI (phantom-deps): Config/tooling dependency; stable pattern for this shared-config package. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Config/tooling dependency; stable pattern for this shared-config package. | ai | |
| phantom-deps | phantom-dep:starpc | AI (phantom-deps): Config/tooling dependency; stable pattern for this shared-config package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): Config/tooling dependency; stable pattern for this shared-config package. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Same rationale as eslint — referenced in shared config files, not directly imported in TS source. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): This package ships shared eslint config; eslint is a runtime dep for consumers, not directly imported in source. | ai |
Versions (showing 100 of 103)
| Version | Deps | Published |
|---|---|---|
| 0.34.2 | 3 / 5 | |
| 0.34.1 | 9 / 6 | |
| 0.34.0 | 9 / 6 | |
| 0.33.1 | 9 / 6 | |
| 0.33.0 | 9 / 6 | |
| 0.32.10 | 9 / 6 | |
| 0.32.9 | 9 / 6 | |
| 0.32.6 | 9 / 6 | |
| 0.32.5 | 9 / 6 | |
| 0.32.4 | 9 / 6 | |
| 0.32.3 | 9 / 6 | |
| 0.32.2 | 9 / 6 | |
| 0.32.1 | 9 / 6 | |
| 0.32.0 | 9 / 5 | |
| 0.31.1 | 9 / 5 | |
| 0.31.0 | 9 / 5 | |
| 0.30.7 | 9 / 5 | |
| 0.30.6 | 9 / 5 | |
| 0.30.5 | 9 / 4 | |
| 0.30.4 | 9 / 4 | |
| 0.30.3 | 9 / 4 | |
| 0.30.2 | 9 / 4 | |
| 0.30.1 | 9 / 4 | |
| 0.30.0 | 9 / 4 | |
| 0.29.0 | 9 / 4 | |
| 0.28.0 | 9 / 4 | |
| 0.27.1 | 9 / 4 | |
| 0.27.0 | 9 / 4 | |
| 0.26.11 | 9 / 4 | |
| 0.26.10 | 9 / 4 | |
| 0.26.9 | 9 / 4 | |
| 0.26.8 | 9 / 4 | |
| 0.26.7 | 9 / 4 | |
| 0.26.6 | 9 / 4 | |
| 0.26.5 | 9 / 4 | |
| 0.26.4 | 9 / 4 | |
| 0.26.3 | 9 / 4 | |
| 0.26.2 | 9 / 4 | |
| 0.24.0 | 9 / 4 | |
| 0.23.0 | 9 / 4 | |
| 0.22.14 | 9 / 4 | |
| 0.22.13 | 9 / 4 | |
| 0.22.12 | 9 / 4 | |
| 0.22.11 | 9 / 4 | |
| 0.22.10 | 9 / 4 | |
| 0.22.9 | 9 / 4 | |
| 0.22.8 | 9 / 4 | |
| 0.22.7 | 9 / 4 | |
| 0.22.6 | 9 / 4 | |
| 0.22.5 | 9 / 4 | |
| 0.22.4 | 9 / 4 | |
| 0.22.3 | 9 / 4 | |
| 0.22.2 | 9 / 4 | |
| 0.22.1 | 9 / 4 | |
| 0.22.0 | 9 / 4 | |
| 0.21.2 | 9 / 4 | |
| 0.21.1 | 9 / 4 | |
| 0.21.0 | 9 / 4 | |
| 0.20.3 | 9 / 4 | |
| 0.20.2 | 9 / 4 | |
| 0.20.1 | 9 / 4 | |
| 0.20.0 | 9 / 4 | |
| 0.19.1 | 9 / 4 | |
| 0.18.8 | 9 / 4 | |
| 0.18.7 | 9 / 4 | |
| 0.18.6 | 9 / 4 | |
| 0.18.5 | 9 / 4 | |
| 0.18.4 | 9 / 4 | |
| 0.18.3 | 9 / 4 | |
| 0.18.2 | 9 / 4 | |
| 0.18.1 | 9 / 4 | |
| 0.18.0 | 9 / 4 | |
| 0.17.3 | 9 / 4 | |
| 0.17.2 | 9 / 4 | |
| 0.17.1 | 9 / 4 | |
| 0.17.0 | 9 / 4 | |
| 0.16.12 | 9 / 4 | |
| 0.16.11 | 9 / 4 | |
| 0.16.10 | 9 / 4 | |
| 0.16.9 | 9 / 4 | |
| 0.16.8 | 9 / 4 | |
| 0.16.7 | 9 / 4 | |
| 0.16.6 | 9 / 4 | |
| 0.16.5 | 8 / 4 | |
| 0.16.4 | 8 / 4 | |
| 0.16.3 | 8 / 4 | |
| 0.16.2 | 8 / 4 | |
| 0.16.1 | 8 / 4 | |
| 0.16.0 | 8 / 4 | |
| 0.15.7 | 8 / 4 | |
| 0.15.6 | 8 / 4 | |
| 0.15.5 | 8 / 4 | |
| 0.15.4 | 8 / 4 | |
| 0.15.2 | 8 / 4 | |
| 0.15.1 | 8 / 4 | |
| 0.15.0 | 8 / 4 | |
| 0.14.11 | 8 / 4 | |
| 0.14.10 | 8 / 4 | |
| 0.14.9 | 8 / 4 | |
| 0.14.8 | 8 / 4 |
v0.34.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.34.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.