@neutron.co.id/pendidikan-modules
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@neon.id/query | AI (dependencies): First-party org dependency in a coherent private ecosystem; stable pattern across versions. | ai | |
| dependencies | unvetted-dep:@neon.id/office | AI (dependencies): First-party org dependency; stable pattern. | ai | |
| dependencies | unvetted-dep:@neon.id/context | AI (dependencies): First-party org dependency; stable pattern. | ai | |
| dependencies | unvetted-dep:@neutron.co.id/tanya-models | AI (dependencies): First-party sibling package; stable pattern. | ai | |
| dependencies | unvetted-dep:@neutron.co.id/jadwal-models | AI (dependencies): First-party sibling package; stable pattern. | ai | |
| dependencies | unvetted-dep:@neon.id/identitas-interfaces | AI (dependencies): First-party org dependency; stable pattern. | ai | |
| dependencies | unvetted-dep:@neutron.co.id/akademik-models | AI (dependencies): First-party sibling package; stable pattern. | ai | |
| dependencies | unvetted-dep:@neutron.co.id/pendidikan-types | AI (dependencies): First-party sibling package; stable pattern. | ai | |
| dependencies | unvetted-dep:@neutron.co.id/penilaian-models | AI (dependencies): First-party sibling package; stable pattern. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.31.2 | 12 / 17 | |
| 1.31.1 | 12 / 17 | |
| 1.30.1 | 12 / 17 | |
| 1.29.23 | 12 / 17 |
v1.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.