@interfere/next
Build software that never breaks.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Move to GitHub Actions CI publish; consistent org repo, no material change. | ai | |
| provenance | missing-githead | AI (provenance): Metadata regression only, no behavioral signal; established publisher and clean codebase. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-trace-otlp-http | AI (phantom-deps): Bundled OTel SDK dep, used via dist build not source imports. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/exporter-logs-otlp-http | AI (phantom-deps): Bundled OTel SDK dep, used via dist build not source imports. | ai | |
| phantom-deps | phantom-dep:@interfere/helpers | AI (phantom-deps): Same-org monorepo dep, resolved via internal build. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/context-async-hooks | AI (phantom-deps): Bundled OTel SDK dep, used via dist build not source imports. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/otlp-exporter-base | AI (phantom-deps): Bundled OTel SDK dep, used via dist build not source imports. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/otlp-transformer | AI (phantom-deps): Bundled OTel SDK dep, used via dist build not source imports. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/sdk-trace-node | AI (phantom-deps): Bundled OTel SDK dep, used via dist build not source imports. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/baggage-span-processor | AI (phantom-deps): Bundled OTel SDK dep, used via dist build not source imports. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/resources | AI (phantom-deps): Bundled OTel SDK dep, used via dist build not source imports. | ai | |
| phantom-deps | phantom-dep:@opentelemetry/api-logs | AI (phantom-deps): Config-referenced OTel dep, consistent FP pattern. | ai | |
| source-diff | obfuscated-file:dist/instrumentation.mjs | AI (source-diff): Minified tsdown build output, not obfuscation; matches stated OTel instrumentation feature. | ai | |
| source-diff | obfuscated-file:dist/internal/build/source-maps/upload.mjs | AI (source-diff): Minified build output implementing documented source-map upload to own API. | ai | |
| phantom-deps | phantom-dep:glob | AI (phantom-deps): Build-tool dependency; referenced in config, stable for this package. | ai | |
| phantom-deps | phantom-dep:@interfere/constants | AI (phantom-deps): Workspace dependency; same org, re-exported via public API. | ai | |
| phantom-deps | phantom-dep:@interfere/types | AI (phantom-deps): Workspace dependency; same org, re-exported via public API. | ai | |
| phantom-deps | phantom-dep:@interfere/react | AI (phantom-deps): Workspace dependency; same org, re-exported via public API. | ai | |
| phantom-deps | phantom-dep:@interfere/sdk | AI (phantom-deps): Workspace dependency; same org, re-exported via public API. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Build-tool dependency; referenced in config, stable for this package. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Utility dependency; referenced in config, stable for this package. | ai | |
| typosquat | typosquat.levenshtein:jest | AI (typosquat): False positive; package is a Next.js integration for the Interfere platform, unrelated to jest. | ai | |
| typosquat | typosquat.levenshtein:knex | AI (typosquat): False positive; package is a Next.js integration for the Interfere platform, unrelated to knex. | ai | |
| typosquat | typosquat.levenshtein:nuxt | AI (typosquat): @interfere/next is a scoped observability SDK, not a nuxt typosquat; name reflects Next.js integration. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 11.0.4 | 20 / 16 | |
| 11.0.3 | 20 / 16 | |
| 11.0.1 | 22 / 16 | |
| 11.0.0 | 22 / 16 | |
| 10.0.0 | 22 / 17 | |
| 9.0.2 | 7 / 17 | |
| 9.0.1 | 7 / 17 | |
| 9.0.0 | 7 / 17 | |
| 8.1.6 | 7 / 17 | |
| 8.1.2 | 6 / 18 | |
| 8.1.0 | 6 / 18 | |
| 8.0.0 | 6 / 19 | |
| 7.0.0 | 6 / 19 | |
| 6.0.0 | 6 / 19 | |
| 5.0.1 | 6 / 19 | |
| 5.0.0 | 6 / 19 | |
| 4.0.0 | 6 / 19 | |
| 3.0.0 | 6 / 19 | |
| 1.0.5 | 7 / 19 | |
| 1.0.4 | 7 / 19 | |
| 1.0.3 | 7 / 19 | |
| 1.0.2 | 7 / 19 | |
| 1.0.1 | 7 / 19 | |
| 1.0.0 | 7 / 19 |
v11.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
4 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (skve) than the most recent previously approved version (GitHub Actions) on 2026-07-10, but skve is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-23. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-21. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-18. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: skve.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-17. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: skve.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.